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
(→GitLab) |
|||
Line 5: | Line 5: | ||
== [[GitLab]] == | == [[GitLab]] == | ||
+ | * 12.8 (Feb 2020) added [[Review Apps]] button | ||
* [[12.5]] [[Delete source branch once merged]] <ref>https://about.gitlab.com/releases/2019/11/22/gitlab-12-5-released/#delete-source-branch-once-merged</ref>, [[feature branches]] are deleted by default to keep your project clean and tidy. | * [[12.5]] [[Delete source branch once merged]] <ref>https://about.gitlab.com/releases/2019/11/22/gitlab-12-5-released/#delete-source-branch-once-merged</ref>, [[feature branches]] are deleted by default to keep your project clean and tidy. | ||
* [https://about.gitlab.com/releases/2019/10/22/gitlab-12-4-released/ 12.4] October 2019 | * [https://about.gitlab.com/releases/2019/10/22/gitlab-12-4-released/ 12.4] October 2019 |
Revision as of 16:25, 19 September 2022
git push -o merge_request.create https://docs.gitlab.com/ce/user/project/push_options.html
GitLab
- 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
Related terms
git merge
git request-pull
- Pull Request (PR)
- GitLab merge queue
Ready to be merged automatically. Ask someone with write access to this repository to merge this request
See also
- 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: