blob: a9d89341397c5985bef32ed3e4152044ad1a9fd0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
---
description: >-
This pages describes how to review PRs to ensure quick and efficient merging.
It is written for both novices and people with experience with GitHub and code
review in general.
---
# Reviewing
For new pull requests to be merged into any of the Northstar repos, they need to reviewed to reduce the changes of introducing bugs as well as ensuring that in case of a feature it's something the community actually wants.
### Process
For a review there's two major parts **code review** and **testing**.
It's not necessary to do both when reviewing as long as you mention what you did when leaving the review comment on GitHub.
#### Code review
For code review head to the _"Files changed"_ section of the PR.
From there you can select the line(s) you want to leave a comment on.
Type in your comment and click on _"Start a review"_.
Note that this will **NOT** post your comment immediately! Add any remaining comments to other lines of code, then head to the _Finishing up_ section of this wiki page to see how to post your code review.
#### Testing
For testing a PR, refer to the following page
{% content-ref url="../testing.md" %}
[testing.md](./testing.md)
{% endcontent-ref %}
The TL;DR is to test the aspect that has been changed.
#### Finishing up
After you performed the testing and/or code review leave a final comment by clicking on _"Finish your review"_ on the top right of the _"Files changed"_ page of the PR.
In your final comment make sure to mention what you did, e.g. which aspects of the change you tested for or what you considered during code review (formatting, edge cases, ...). The more detailed this part is the easier it is for other reviewers to tell which aspects they can skip during reviewing to speed up the process.
After leaving your comment, select the type of feedback.
* **Comment**: General remarks, use if neither of the later two applies.
* **Approve**: You found no issues when looking at the code or during testing.
* **Request changes**: Either something in the code doesn't look right or you found bugs during testing.
{% hint style="warning" %}
Approval reviews should **always** contain information about what parts of the code you looked at or tested. Approvals without comment or a single _LGTM_ are not useful and will be dismissed. \
Some exceptions to this rule are e.g. approving a single line comment typo fix, though even than the review should say something along the lines of "LGTM as it's just single line typo fix in a comment". In a nutshell it should be obvious to a future reader why you approved a PR without the reader having to look at the file diff first.
Contributors with reviewer access may see their role removed should they leave (multiple) empty/_"LGTM"_ reviews.
If you want to "approve" a pull request because you like the feature it implements, please opt for simply giving the PR a "👍" reaction instead.
{% endhint %}
Finally, click on _"Submit review"_. Your review is now publicly visible, congrats! :D
|
