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

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

Download file

             open-pull-request.rst
        
                    34 lines
            
             | 1.1 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / collaboration / open-pull-request.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      .. _open-requests-ref:

      Open a |pr|

      -----------

      .. important::

         To open a |pr|, it is necessary that the source and the target repositories

         have at least one commit in common. For more information,

         see :ref:`merging-empty-repo-ref`.

      Once you have finished your work on a fork and want your work merged with the

      original |repo|, you need to open a |pr|. To open a |pr| and send for

      review, use the following steps:

      1. Select

         :menuselection:`Admin --> repositories --> repo name --> Options --> Create Pull Request`

      2. On the :guilabel:`New Pull Request` page, enter the following information:

         * The |pr| name.

         * The |pr| description.

         * Add the reviewer names in the :guilabel:`Pull Request Reviewer` field.

      3. Review the changesets that make up the |pr|.

      4. Select :guilabel:`Submit Pull Request`.

      .. image:: ../images/open-pr.png

         :alt: Open a pull request

      The pull request can either be merged into the original repository,

      or it can be declined due to issues during the review process. If issues

      arise, you can fix them and update the |pr|. For more,

      see :ref:`update-requests-ref`.

	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	.. _open-requests-ref:

		Open a \|pr\|
		-----------

		.. important::

		To open a \|pr\|, it is necessary that the source and the target repositories
		have at least one commit in common. For more information,
		see :ref:`merging-empty-repo-ref`.


		Once you have finished your work on a fork and want your work merged with the
		original \|repo\|, you need to open a \|pr\|. To open a \|pr\| and send for
		review, use the following steps:

		1. Select
		:menuselection:`Admin --> repositories --> repo name --> Options --> Create Pull Request`
		2. On the :guilabel:`New Pull Request` page, enter the following information:

		* The \|pr\| name.
		* The \|pr\| description.
		* Add the reviewer names in the :guilabel:`Pull Request Reviewer` field.

		3. Review the changesets that make up the \|pr\|.
		4. Select :guilabel:`Submit Pull Request`.

		.. image:: ../images/open-pr.png
		:alt: Open a pull request

		The pull request can either be merged into the original repository,
		or it can be declined due to issues during the review process. If issues
		arise, you can fix them and update the \|pr\|. For more,
		see :ref:`update-requests-ref`.