Skip to content

Commit 5bc956d

Browse files
Reference LOGAF Scale from develop docs (#15154)
Link to the Sentry develop docs for explaining the LOGAF scale.
1 parent 2e708dc commit 5bc956d

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

docs/pr-reviews.md

+2-6
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,8 @@
22

33
Make sure to open PRs against `develop` branch.
44

5-
For feedback in PRs, we use the [LOGAF scale](https://blog.danlew.net/2020/04/15/the-logaf-scale/) to specify how
6-
important a comment is:
7-
8-
- `l`: low - nitpick. You may address this comment, but you don't have to.
9-
- `m`: medium - normal comment. Worth addressing and fixing.
10-
- `h`: high - Very important. We must not merge this PR without addressing this issue.
5+
For feedback in PRs, we use the [LOGAF scale](https://develop.sentry.dev/engineering-practices/code-review/#logaf-scale) to specify how
6+
important a comment is.
117

128
You only need one approval from a maintainer to be able to merge. For some PRs, asking specific or multiple people for
139
review might be adequate. You can either assign SDK team members directly (e.g. if you have some people in mind who are

0 commit comments

Comments
 (0)