Support reviewer groups in Github
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 52
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 54
Description
Phabricator reporter is able to set specific reviewer groups on the revision when a specific linter fails.
Only the taskgraph diff task currently uses that feature.
The github reporter should support this feature, when the groups are available (ideally sharing the same name/slug as Phabricator)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reviewer-group handling in bot/code_review_bot/report/phabricator.py at lines 174-195 and the taskgraph diff reference in bot/code_review_bot/tasks/tgdiff.py at line 87. Compare the GitHub reporter behavior discussed in pull request 3382. Done means the GitHub reporter uses available reviewer groups, ideally with the same names or slugs as Phabricator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100