pr-triage
Workflow
- Set the environment variable GH_API_TOKEN to a token with public_repo access.
- Run index.js
- Fix any assertions on github, then re-run.
- Run histogram.js, move.js or stale.js
OLD
- Run index.js.
- Fix any assertions on github, then re-run.
- Compare pulls.json (old) to output.json (new).
- Copy output.json over pulls.json.
- Check in all changed files, delete output.json.
Doesn't include notes or flags
- survey JS usage of @link @see to see how people might 'intuitively' expect it to work
- talk with Andrew about how to (1) parse as expression (2) surface to the language service
- write up our conclusions as a proposal and try to get upvoters to comment
Goals
- Less than 100 (50?) open PRs. 1a. Less than 100 (50?) open, labelled PRs.
- All community PRs older than a week triaged.
- All team PRs older than two weeks triaged.
- All triaged PRs assigned to a team members.
- All team members get an update once a week or more on their individual progress.
- All PRs that have been in the Waiting state for more than 14 days are closed.
Triaged means:
- On project board in Needs Review state or later.
- Labelled with "For Milestone Bug", "For Backlog Bug", "For Uncommitted bug", "Experiment" or "Housekeeping".
Progress
In 7 weeks:
- 110 PRs closed so far
- Tracked categories decreased from 167 to 102
- all goals except (1) and (6) are true