If the source branch is not ahead of the target branch, merge requests cannot be created. Resolving Requests That Cannot Be Automatically Merged If a conflict is found after the source branch is compared with the target branch, the system will indicate that they cannot be automatically merged. ...
You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch. Who can use this feature? ...
Describe the bug At some point there was a change that broke the clang workflow for2.7-branch. It has not been a high priority. However, there are backports that cannot be merged until CI is green. From what I can tell, the clang workflow simply times-out whenever it is run. Please a...
Because he/she did not rebase on the branch and give the CI system the opportunity to vet the automatic merged changes. It took a couple hours to diagnose and correct that issue, during which time, no one was able to do any merges to master, backing up the pipeline for a while. So ...
approving reviews will be dismissed as stale if the merge base introduces new changes after the review was submitted. The merge base is the commit that is the last common ancestor between the topic branch and the base branch. If the merge base changes, the pull request cannot be merged until...
Merge the local branch with the remote upstream branch. For the merge to succeed, the tip of the remote branch cannot be behind the branch you want to push. The syntax is: git merge <remote_name>/<remote_branch> For example, to merge with thefeaturebranch in theoriginremote repository, ...
It cannot be deleted. It’s initially protected against forced pushes. When a merge request uses an issue closing pattern to close an issue, the work is merged into this branch. The name of your new project’s default branch depends on any instance-level or group-level configuration chang...
How to run merge request pipelines on source branch and merged_result GitLab CI/CD ci , merge-requests , pipelines , merge-train 0 2479 July 11, 2022 Run a branch pipeline only if not a merge request? GitLab CI/CD 2 2855 August 1, 2023 Pipelines must succeed -- which ones?
I've tried this out and cannot replicate the bug in any way. There is also no reason (confirmed after checking the code) for develop to be merged into master when you run the checkout action. There also isn't any changes that I could think could possibly be related to this that were...
Merge Request cannot be merged because it erroneously displays Source branch does not exist. Please restore it or use a different source branch What is the expected correct behavior? Merge button should be active and there should be no Source branch does not exist. Please restore it or use a...