Beta uplift nag template should suggest asking for release uplift if we're in RC week (and mention that we're in RC week)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
As per summary. Example: https://bugzilla.mozilla.org/show_bug.cgi?id=1992036#c5
At this point (Tue in RC week), it's too late for beta uplifts. Release uplifts would still work but of course the bar is quite high...
The comment should be clear about both of those (and definitely not suggest asking for beta uplift)
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
In the mozilla/bugbot repository, locate the beta uplift nag template and any tests covering its generated comment. Read the existing uplift timing logic first; done means the RC-week comment identifies the timing, avoids suggesting a beta uplift, and points to release uplift instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100