Feb 27, 2025 · Problem to solve I’m trying to set my repo up so that it will only allow merges to the main branch via merge requests. Is that possible? I can only find settings for allowing merges and pulls altogether, no settings that limits users from merging directly.

Jun 18, 2019 · I would like to make a rule where, these feature branches would not be able to create merge request directly to the master branch. If a feature needs to be deployed to production, it must first be merge to dev and then make a merge request from dev to master.

Mar 22, 2022 · I am trying to implement git flow with GitLab. The flow of merge requests should be restricted. For example, it should not be allowed to create a merge request from a feature branch to main. Can I solve this with git server side hooks?

To get your branch merged into the main branch: Go to the page provided in the link that was provided by Git and create your merge request. The merge request’s Source branch is your branch and the Target branch should be the main branch. If …

May 2, 2018 · I would like to know what strategy you use when you want to block any push/merge to master when pipeline fails. I mean, I have a project with everything configured and correct, but if someone with DEVELOPER access level does the steps below, he/she will be able to merge into master without pipeline had been ran.

GitLab merge requests commonly follow one of these flows: Working with protected branches in a single repository. Working with forks of an authoritative project. Protected branch flow With the protected branch flow, everybody works in the same GitLab project, instead of forks.

Mar 15, 2024 · Hello, I’m wondering if Gitlab has a feature where you can restrict a merge request to only have a specific source branch to a specific target branch. Let me explain here.

Currently, if an MR does not contain a pipeline it cannot be merged. With :changes keyword, users can control what kind of changes the pipeline/individual jobs would run for.

Oct 26, 2023 · When creating a merge request manually in the UI I see the merge blocked until the pipeline terminates and succeeds to be have the merge button enabled. However, when using Merge Requests API the attribute merge_when_pipeline_succeeds is always set to false when calling a GET /projects/:id/merge_requests/:merge_request_iid.

My problem is that I thought master branch was protected by pipelines as job was configured on master only and option 'Only allow merge requests to be merged if the pipeline succeeds' was checked. Is there any option to achieve it? regards.