Global GitLab Integration?

Ideas Feature Requests
,
1

Since all topics about GitLab cross-repository access are closed, let’s open a new one.

There is still the issue that cloud-agents create GitLab Cursor users scoped to the repository, which prevents running pipelines where repositories include pipeline templates from another project (of the same organization).

Making that template-repository public is definitely NOT an option. The proposed workaround with e GitLab JobToken (as seen here: GitLab broken CI on Cursor created merge request - #7 by mohitjain ) does not work either, because `includes` are being resolved before any job started, on behalf of the user who invoked it (in this case Cursor (@project_xyz_abc12345)) which then fails.

It would be nice if the actual integration could be configur@project_xyz_abc12345d to either be per organization,group or repository.

Pairing it with a Service Account would already help I think…

Any chance to get an upgraded integration in the near future?

6

It’s been over a week now without any response.

Are there any news on it? Is it planned to be fixed/updated? Or will you focus on GitHub instead?

7

Hey @Michael_CMRG!

This category is for requesting features, where users can vote if they share a similar need or pain point. Please note that posting here doesn’t necessarily guarantee a response.

We’re planning a lot of QOL improvements to our SCM improvements (across all supported SCMs). I can’t speak to any specific plans around the Gitlab integration just yet.

8

Got it! That clears up the silence! :slight_smile:

Thanks for the response! Looking forward to the improvements then!
Thread can be closed I think.