Joey Armstrong | 34f1840 | 2023-07-21 18:58:10 -0400 | [diff] [blame] | 1 | .. _pull-request-see-also: |
| 2 | |
Joey Armstrong | 36592e3 | 2022-11-28 09:00:28 -0500 | [diff] [blame] | 3 | VOLTHA project repositories |
| 4 | =========================== |
| 5 | |
| 6 | Development and code reviews: |
| 7 | ----------------------------- |
| 8 | |
Joey Armstrong | 34f1840 | 2023-07-21 18:58:10 -0400 | [diff] [blame] | 9 | :ref:`Commit message syntax <pull-request--commit-message>` |
| 10 | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
Joey Armstrong | 36592e3 | 2022-11-28 09:00:28 -0500 | [diff] [blame] | 11 | |
Joey Armstrong | 3980d70 | 2023-08-23 10:57:18 -0400 | [diff] [blame] | 12 | - `Working url (branch=master fallback) <https://docs.voltha.org/master/howto/code/commit-message.html#pull-request-commit-message>`_ |
| 13 | |
Joey Armstrong | 34f1840 | 2023-07-21 18:58:10 -0400 | [diff] [blame] | 14 | Job directives: recheck |
| 15 | ----------------------- |
Joey Armstrong | 36592e3 | 2022-11-28 09:00:28 -0500 | [diff] [blame] | 16 | |
Joey Armstrong | 34f1840 | 2023-07-21 18:58:10 -0400 | [diff] [blame] | 17 | If the CI check did not launch or failed and you believe the issue is |
| 18 | unrelated to your patch/changeset you can re-trigger the job by commenting |
| 19 | on the patch with *recheck*. |
Joey Armstrong | 36592e3 | 2022-11-28 09:00:28 -0500 | [diff] [blame] | 20 | |
Joey Armstrong | 34f1840 | 2023-07-21 18:58:10 -0400 | [diff] [blame] | 21 | - Visit gerrit: https://gerrit.opencord.org/c/bbsim/+/34384 |
| 22 | - Click the pencil icon in the top left by reviewers. |
Joey Armstrong | 3980d70 | 2023-08-23 10:57:18 -0400 | [diff] [blame] | 23 | - Comment/description text: ``recheck`` |
Joey Armstrong | 36592e3 | 2022-11-28 09:00:28 -0500 | [diff] [blame] | 24 | |
Joey Armstrong | 34f1840 | 2023-07-21 18:58:10 -0400 | [diff] [blame] | 25 | It may take a little while to run dependent on queue size but this token will |
| 26 | initiate re-running job phases for a patch. |
Joey Armstrong | 3980d70 | 2023-08-23 10:57:18 -0400 | [diff] [blame] | 27 | |
| 28 | Code Review Request |
| 29 | ------------------- |
| 30 | |
| 31 | A code review can be requested in two ways, interactively when a patch is |
| 32 | created or from the gerrit UI. Item of note, gerrit will also automatically |
| 33 | assign reviewers based on volume of commits to an individual repository so |
| 34 | you may have reviewers w/o explicitly requesting one. |
| 35 | |
| 36 | Interactively using git |
| 37 | ----------------------- |
| 38 | |
| 39 | - Create a patch, rebase/merge as needed. |
| 40 | - git review to create a pull request. |
| 41 | |
| 42 | - From the command line, include argument --reviewers |
| 43 | - git review --reviewers tux@onf.org foo@onf.org bar@onf.org |
| 44 | - People will be notified via email about the review request. |
| 45 | |
| 46 | Manually add reviewers at a later date |
| 47 | -------------------------------------- |
| 48 | |
| 49 | - `Naviagate to your patch in gerrit <https://gerrit.opencord.org/c/bbsim/+/34384>`_ |
| 50 | - Click the pencil icon in the top left by reviewers. |
| 51 | - Add community members to request a review. |
| 52 | |
| 53 | |