rhodecode-enterprise-ce Files · docs/collaboration/pull-requests.rst

pull-requests: loosen strict view of pull-requests that state is changing...

pull-requests: loosen strict view of pull-requests that state is changing - we now replace it with limited view which still allows deletion/editing of reviewers or title and description - added labels for state changing instead of grey out (it was used for closed PRs) - small UI fixes

marcink - - Load All Authors

File last commit:

r1:854a839a default


                r4103:78e087c7

default

Download file

             pull-requests.rst
        
                    29 lines
            
             | 714 B
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / collaboration / pull-requests.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      .. _pull-requests-ref:

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

      .. toctree::

          pr-flow

          pull-req-mgmt

          open-pull-request.rst

          review-pull-request.rst

          update-pull-request

          approve-pull-request.rst

          merge-pull-request.rst

          fixing-common-commits.rst

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

marcink project: added all source files and assets	r1	.. _pull-requests-ref:

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

		.. toctree::

		pr-flow
		pull-req-mgmt
		open-pull-request.rst
		review-pull-request.rst
		update-pull-request
		approve-pull-request.rst
		merge-pull-request.rst
		fixing-common-commits.rst