##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
settings: re-use attached request global config for performance...
settings: re-use attached request global config for performance - since we *always* generate a global config and register it into request make use of it, and not rely on the get_all_settings heavy logic that makes it slow to fetch because of cache checks. Within single request we're fine to re-use it when ever request attribute is available
marcink - - Load All Authors

File last commit:

r1:854a839a default
r4200:007322e6 stable
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|.