gitlab-ci

I noticed that when CML produces the reports (as per in cml-send-comment --update --pr report.md) such reports are shown in the PR conversation as belonging to a certain user rather than GitHub actions reports. Is this intended behaviour or is there a setting/flag where we can choose which user to assign to the comments reports?

I haven't figured out how such user is chosen, I suspect it is t

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

Hi,

We are using terraform-aws-gitlab-runnner to spin up GitLab runners on our AWS account. As part of security auditing, there was a severe alert raised on this policy created by terraform module: https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/policies/instance-docker-machine-policy.json#L21

The problem lies with permitting IamPassrole action on all resources. As per