Store delegator(s) somewhere.
Open
Nobody has claimed this yet.
mergebot
- Dominant language
- Python
- Stars
- 159
- Forks
- 156
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 16
Description
Currently if a reviewer delegates on a PR, they are not tracked and will not be held responsible for outstanding forward ports etc...
They should probably be stored, and also made part of the spam-set alongside the author and reviewer(s).
Contributor guide
No contributing guide indexed for this repository
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 by tracing how PR reviewers delegate work and how outstanding forward ports are tracked. Then inspect the existing spam-set handling for authors and reviewers. Done means delegators are stored and included in that spam-set so they remain responsible for outstanding forward ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100