gitlab

It would be good if Gitea offered support for the new citation file format, cf. https://citation-file-format.github.io/ and https://blog.front-matter.io/mfenner/step-forward-for-software-citation

This is intended to allow scientists to cite software repositories. I can imagine an implementation similar to Github: Similar to the buttons for forks and downloads of repositories, there may be a new

Describe the proposed change(s).

Today we use re2 for any user-provided regex, with the aim being we can't be the victim - intentionally or accidentally - of catastrophic backtracking.

But how do we make sure that we don't accidentally add a problematic regex in our own code? Wouldn't we essentially close off the risk if we used re2 for any complex regex instead of using regex literals

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

Description of the problem, including code/CLI snippet

Documentation is missing an example how to make use of project import parameters.
The Gitlab-API supports these parameters (name,file,path,overwrite)

Expected Behavior

It would be good to add an example to the documentation (if those parameters are supported)

Actual Behavior

Specifications

• python-gitlab versi

Describe the feature or problem you'd like to solve
My team has its issue board not on a specific repo, but on a group above the repos, currently it seems that glab doesn't allow selecting issue boards on groups, only on repos, so I can't display our issue board.

Propose a Solution
Find issue boards from all parent groups for the repo that is the currently open folder in the terminal,

#197 took care of being able to use # at the start of a line, but I just noticed that there isn't a great user flow for editing an issue that already has markdown headings.

1. Create an issue with at least 1 heading
2. Edit the issue with lab issue edit [ID]
3. Make changes and save
4. The issue will now have its heading(s) stripped out

I'm not sure what the best course would be, but

scala-steward-org/scala-steward#2237 (comment)

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

Currently if you try to clone a repository from github and you don't have any ssh keys configured at github, you will fail to clone and get such message:

Fatal error: fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Even Permission denied (publickey). message is not shown.

@guyzmo offered to "suggest a