##// END OF EJS Templates
u » pc » rhodecode-enterprise-ce-fork-pc
RSS

Fork of rhodecode-enterprise-ce

shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r2777:f1cc2e3d 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|.