##// END OF EJS Templates
fix(permissions): added a common way to update private flag via repo model...
fix(permissions): added a common way to update private flag via repo model - this allows to have a one and only one way to control the flag with the business logic shared - added test for that - changed view to use this method instead of DB update and custom permissions flush - fixed a case when update of repo settings didn't flush permissions actually while it should when private flag changed

File last commit:

r1:854a839a default
r5551:5b9b5ed2 default
Show More
pull-requests.rst
29 lines | 714 B | text/x-rst | RstLexer

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|.