gitlab

Feature Description

Hi,

I'm monitoring my Gitea instance via Prometheus and Grafana.
It would be great to have a string for the current Gitea version and the new one in the metrics to set an Grafana alert for possible new version on it.

Screenshots

No response

Describe the proposed change(s).

• aws-machine-image
• cargo
• composer
• docker
• git
• gradle #13554
• hashicorp
• helm
• hex #13394
• ivy
• loose #13454
• maven #13332
• node #13404
• npm #13404
• nuget
• pep440 #13409
• poetry
• regex
• rez #13334
• `r

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

Currently we have a lot of unimplemented tests in tests/unit/test_projects.py.

Adding these tests would be a good first issue for someone to work on.

Comment below if you would like to work on this issue.

Create Gitlab Push/Pull Mirrors

I have a need to recreate a lot of repositories with pull mirroring. This tool has all the other pieces I need except this one feature.

Propose a Solution

Using `glab repo mirror --direction=pull --src="ssh://git@gitlab.example.com:2222/namespace/project.git" --auth=ssh --allow-divergence --protected-branches-only my-new-namespace/my-new-project-na

#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

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.