<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=479907) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154111, we added the ability for CI_JOB_TOKEN to make git pushes to its own repository. The feature flag `push_repository_for_job_token_allowed` was introduced in v17.2 In the associated issue for this functionality, https://gitlab.com/gitlab-org/gitlab/-/issues/389060, there are multiple conversations about a future iteration where the CI_JOB_TOKEN can be used to push git changes to other repositories, if the originating repository is on the target repository's [job token allowlist](https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html#add-a-group-or-project-to-the-job-token-allowlist). Issue threads about this: - https://gitlab.com/gitlab-org/gitlab/-/issues/389060#note_1398134444 - https://gitlab.com/gitlab-org/gitlab/-/issues/389060#note_1760932298 Several customers have expressed interest in this capability: - https://gitlab.com/gitlab-org/gitlab/-/issues/389060#note_1586379595 - https://gitlab.com/gitlab-org/gitlab/-/issues/389060#note_1763444273 - https://gitlab.zendesk.com/agent/tickets/458069 (internal) - https://gitlab.zendesk.com/agent/tickets/559609 (internal) <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->