Print a summary in the dry-run mode
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
@calixteman:
Maybe we could add something likeWhat is the number of touched bugs when it'll run for the 1st time ?in order to avoid to overflow bugzilla.
Nice! Maybe we could create a small summary in the dry-run mode and ask the author to copy-paste it into the PR. The summary could include something like:
- Number of bugs in the initial query
- Number of bugs after the filtering
- Number of nag emails
- Number of auto-fix actions
- Number of needinfo requests
Originally posted by @suhaibmujahid in https://github.com/mozilla/relman-auto-nag/issues/1420#issuecomment-1119559590
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 locating the Python entry point that implements dry-run mode and trace how the initial query, filtering, nag emails, auto-fix actions, and needinfo requests are counted. Done means dry-run output includes those five summary values and the relevant tests cover the displayed results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100