-
Notifications
You must be signed in to change notification settings - Fork 8
in-review label: how and when to use it #48
Copy link
Copy link
Closed
Labels
discussShare your constructive thoughts on how to make progress with this issueShare your constructive thoughts on how to make progress with this issueenhancementNew feature or enhancement of existing functionalityNew feature or enhancement of existing functionalityhelp wantedIf you can help make progress with this issue, please comment!If you can help make progress with this issue, please comment!
Metadata
Metadata
Assignees
Labels
discussShare your constructive thoughts on how to make progress with this issueShare your constructive thoughts on how to make progress with this issueenhancementNew feature or enhancement of existing functionalityNew feature or enhancement of existing functionalityhelp wantedIf you can help make progress with this issue, please comment!If you can help make progress with this issue, please comment!
The
in-reviewlabel is reserved for the team member / QA reviewing the Pull Request code/change. The reviewer applies the label to communicate with the rest of the team that they are actively reviewing the PR and to avoid duplication of effort.We used to require reviewers to write a comment on the PR (typically a 👀
:eyes:emoji) to indicate that they were reviewing the PR, but we decided that using a label instead of a comment was clearer (especially to non-technical team members/stakeholders) and worked well for us.Process Automation
enhancementhelp wantedOnce the pull request has been merged @dwylbot 🤖 will remove the
in-reviewlabel from the Pull Request and apply theplease-testlabel. 🛎Additionally/Optionally @dwylbot 🤖 will parse the commit messages in the PR for any issue numbers and apply the
please-testlabel to those issues too. ✨