##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
pull-requests: changed the order of close-branch after merge, so we don't leave open heads....
pull-requests: changed the order of close-branch after merge, so we don't leave open heads. Branches will be closed, and then merged based on the close commit. This is a proper and recommended workflow for feature branches and close option.
marcink - - Load All Authors

File last commit:

r3290:ac4e4e5a default
r4436:37e7e17e default
Show More
merge-pull-request.rst
35 lines | 1.2 KiB | text/x-rst | RstLexer
/ docs / collaboration / merge-pull-request.rst
History | Annotation | Raw |Copy content |Copy permalink

Merge a |pr|

|RCE| can detect if it can automatically merge the changes in a |pr|. If it can, you will see the following message: :guilabel:`This pull request can be automatically merged.` To merge, click the big blue button! To enable this feature, see :ref:`server-side-merge`.

../images/merge-pr-button.png

If you cannot automatically merge a |pr|, you will see one of the following messages:

  • :guilabel:`This pull request cannot be merged because of conflicts`
  • :guilabel:`Reviewer approval is pending`

Manual Merge a |PR|

If |RCE| cannot safely merge the changes in a |pr|, usually due to conflicts, you need to manually merge the changes on the command line. You can see more information for each |repo| type at the following links: