27 lines
1 KiB
ReStructuredText
27 lines
1 KiB
ReStructuredText
.. _code-review-ref:
|
|
|
|
Code Review
|
|
===========
|
|
|
|
|RCE| 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
|
|
:ref:`extensions-hooks-ref` sections for examples on how to set this up.
|
|
|
|
.. 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/
|