rhodecode-enterprise-ce Files · docs/code-review/code-review.rst

dependencies: bumped test dependencies...

dependencies: bumped test dependencies - pytest==3.6.0 - py==1.5.3 - removed: pytest-catchlog==1.2.2 - pytest-sugar==0.9.1 - pytest-runner==4.2.0 - pytest-profiling==1.3.0 - pytest-timeout==1.2.1

dan - - Load All Authors

File last commit:

r552:9a0f45b0 default


                r2761:cdb0bfef

default

Download file

             code-review.rst
        
                    27 lines
            
             | 1.0 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / code-review / code-review.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        marcink
    
project: added all source files and assets

              r1
            
      .. _code-review-ref:

      Code Review

      ===========

      |RCM| provides two ways in which you can review code. You can review |prs| or

      commits. To better understand |prs|, see the :ref:`pull-requests-ref`

      and :ref:`collaborate-ref` sections. For more information about why

      code review matters, see these posts on the topic:

      * `Code Review - Fix Bugs Early and Often`_

      * `Code Review - How to Convince a Skeptic`_

      * `Code Review - Learn How NASA Codes`_

      You can also use the |RCE| API set up continuous integration servers to leave

      comments from a test suite. See the :ref:`api` and

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
      :ref:`extensions-hooks-ref` sections for examples on how to set this up.

        marcink
    
project: added all source files and assets

              r1
            
      .. toctree::

         review-diffs

         approve-changes

         reviewing-best-practices

      .. _Code Review - Fix Bugs Early and Often: https://rhodecode.com/blog/code-review-fix-bugs-early-often/

      .. _Code Review - How to Convince a Skeptic: https://rhodecode.com/blog/code-review-convince-skeptic/

      .. _Code Review - Learn How NASA Codes: https://rhodecode.com/blog/code-review-learn-nasa-codes/

	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	.. _code-review-ref:

		Code Review
		===========

		\|RCM\| provides two ways in which you can review code. You can review \|prs\| or
		commits. To better understand \|prs\|, see the :ref:`pull-requests-ref`
		and :ref:`collaborate-ref` sections. For more information about why
		code review matters, see these posts on the topic:

		* `Code Review - Fix Bugs Early and Often`_
		* `Code Review - How to Convince a Skeptic`_
		* `Code Review - Learn How NASA Codes`_

		You can also use the \|RCE\| API set up continuous integration servers to leave
		comments from a test suite. See the :ref:`api` and
dan docs: updated docs for integrations, fixes #4137...	r552	:ref:`extensions-hooks-ref` sections for examples on how to set this up.
marcink project: added all source files and assets	r1
		.. toctree::

		review-diffs
		approve-changes
		reviewing-best-practices

		.. _Code Review - Fix Bugs Early and Often: https://rhodecode.com/blog/code-review-fix-bugs-early-often/
		.. _Code Review - How to Convince a Skeptic: https://rhodecode.com/blog/code-review-convince-skeptic/
		.. _Code Review - Learn How NASA Codes: https://rhodecode.com/blog/code-review-learn-nasa-codes/