Difference between revisions of "Merge Request (MR)"
Jump to navigation
Jump to search
↑ https://about.gitlab.com/releases/2019/11/22/gitlab-12-5-released/#delete-source-branch-once-merged
| Line 19: | Line 19: | ||
* <code>[[git merge]]</code> | * <code>[[git merge]]</code> | ||
* <code>[[git request-pull]]</code> | * <code>[[git request-pull]]</code> | ||
| − | * [[Pull Request (PR)]] | + | * [[Pull Request (PR)]]: <code>[[gh pr create]]</code> |
* [[GitLab merge queue]] | * [[GitLab merge queue]] | ||
* <code>[[Ready to be merged automatically. Ask someone with write access to this repository to merge this request]]</code> | * <code>[[Ready to be merged automatically. Ask someone with write access to this repository to merge this request]]</code> | ||
Latest revision as of 08:59, 25 January 2023
git push -o merge_request.create origin my-branch error: src refspec my-branch does not match any error: failed to push some refs to 'github.com:your-repo/your-project.git'
git push -o merge_request.create https://docs.gitlab.com/ce/user/project/push_options.html
GitLab[edit]
- 12.8 Feb 2020 added Review Apps button
- 12.5 Delete source branch once merged [1], feature branches are deleted by default to keep your project clean and tidy.
- 12.4 October 2019
- Merge Request Dependencies
MR approvals requires GitLab premium licence
Related terms[edit]
git mergegit request-pull- Pull Request (PR):
gh pr create - GitLab merge queue
Ready to be merged automatically. Ask someone with write access to this repository to merge this request
See also[edit]
- Branch, MR,
git branch, Managing a branch protection rule in GitHub - Merge Request (MR), GitLab merge queue:
git merge,git merge main,git merge origin/main,git merge main --allow-unrelated-histories - Merge Request,
git merge
Advertising:
