Ability to set "merge_when_build_succeeds" as project's option
Certain use cases rely in Git repositories to keep version controlled configuration files that change and/or growth frequently, and are consumed by 3rd party systems. For this cases, GitLab CI in combination with merge requests can be used to ensure a controlled edition or addition of elements (avoid conflicts) and also verify that the syntax/format of what is introduced is valid.
Users of the system will provide their configuration elements to the repository via topic branches and issue a MR to the master branch. A GitLab CI job will verify the syntax of the changes proposed and if valid, the MR can be merged.
This process could be fully automatized as no human verification is needed.
Nowadays, a merge request can be flagged with merge_when_build_succeeds
, which will cause the MR to be merged when all the CI tests are successfully finished. However, this can only be set once the MR has been created.
We request to have the possibility to set a default value for that flag in the projects level. GitLab projects would implement a flag "Merge when CI build success" available in the project's settings page (Merge Request section). When a new merge request is created, the value of this flag (in the target project) will be used to feed the merge_when_build_succeeds
field for the merge request object (which now has false
as default).
The whole behaviour of the merge_when_build_succeeds
feature will stay the same. Just its initial value will be taken from the default value set in the target project's new setting.
Thanks,
CERN VCS Team