##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
pull-requests: fixed case for GIT repositories when a merge check failed due to merge conflicts the pull request wrongly reported missing commits....
pull-requests: fixed case for GIT repositories when a merge check failed due to merge conflicts the pull request wrongly reported missing commits. - we're now searching for dangling commits in a repo that has them and cannot see them because of failed merge checks. - pull-request: will save metadata during merge simulation so merge conflicts are permanently stored, and showed to all users.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r4299:04e45b92 default
Show More
pull-requests.rst
29 lines | 714 B | text/x-rst | RstLexer
/ docs / collaboration / pull-requests.rst
History | Annotation | Raw |Copy content |Copy permalink

Pull Requests

Once a |pr| is open, you can use a variety of different code review functions to ensure the quality or style of code is appropriate for your standards. The |pr| is then merged with the main branch when it is approved. The following steps are an overview of the workflow:

  1. Create a fork or branch of a |repo|.
  2. Complete your works and open a pull request.
  3. Notify users to review and approve the |pr|.
  4. Merge the code to the target |repo|.