### Problem to solve Presently the repository mirroring option (auto-push) does not allow specification of `--push-options`. It would be nice to have this. ### Intended users Unknown ### Further details One application of this is when using repository mirroring to push to another GitLab repository. It would then be nice to have the option of avoiding triggering the CI pipelines. This is useful e.g. if the target repository does not allow the same runners as the source repository. Skipping the CI pipelines can be accomplished using `--push-options ci.skip` as documented [here](https://docs.gitlab.com/ee/ci/yaml/#skipping-jobs) ### Proposal Add a field `push options` in the repository mirroring settings. The user can then use this field to set custom push options. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references