rust-lang / rust-lang/rustc-pr-tracking
Track review activity
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
It's common for the last activity on a PR to be irrelevant:
- comment from triage asking for status
- author asking for status
- rustbot informing about a merge conflict
- author fixing a merge conflict
Ideally, we would track review activity:
- exclude comments by the author
- exclude rustbot comments
- exclude comments by others with certain keywords like "triage", "status", "bump", etc
- include all activity by the assigned reviewer
- include code-review activity
- exclude drafts
This obviously isn't possible with the basic Github filters available, but I think it would give us a much better idea of how long PRs are sitting without activity. Merge conflict notifications alone likely result in a de-facto upper limit to time-since-updated.
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
The issue does not name any files, tests, or entry points. Start by locating the code that determines PR activity and review timing, then compare its current behavior with the requested exclusions and inclusions. Done means review activity is tracked without author, rustbot, status-related, merge-conflict, or draft noise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100