Remove good-first-bug from whiteboard
Categories
(bugzilla.mozilla.org :: Bulk Bug Edit Requests, task, P3)
Tracking
()
People
(Reporter: emceeaich, Assigned: kohei)
References
Details
(Keywords: good-first-bug)
Make sure that in bugs that still have good-first-bug or similar in whiteboard have the good-first-bug keyword and remove it from the whiteboard.
|
||
Updated•6 years ago
|
|
Assignee | |
Comment 1•6 years ago
|
||
There are only 18 open bugs that have good-first-bug in the Whiteboard. Can be removed manually.
|
Reporter | |
Comment 2•6 years ago
|
||
The list of bugs is: https://mzl.la/2LhCWME
If you take this task, update the whiteboard field, removing good-first-bug and cases such as [good-first-bug]. Then add the good-first-bug keyword.
|
|
Reporter | |
Updated•6 years ago
|
|
||
Comment 3•6 years ago
|
||
Hi @emceeaich,
I would like to work on this bug
|
|
Reporter | |
Comment 4•6 years ago
|
||
Hi, Anurag.
Please write a script that can make the changes using the Bugzilla API.
You script should go in https://github.com/mozilla-bteam/bmo/tree/master/scripts so make a fork and submit a pull request when you're ready. Link the URL of the pull request as the text of an attachment to this bug.
Once you have your pull request, ready and posted, we'll make you the assignee for the bug.
To try out your script, you can log into https://bugzilla-dev.allizom.org/, set up an API key there, or you can check out your branch of Bugzilla and run it in a container on your computer. You'll want to create some bugs as test cases, making sure to include edge cases to check.
Thanks!
|
|
Reporter | |
Comment 5•5 years ago
•
|
||
This stalled, so I'm just going to write an autonag module to run it.
|
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Comment 6•5 years ago
|
||
This is still available as a good first bug.
Since this was filed, we have a new framework for bulk bug edits, https://github.com/mozilla/relman-auto-nag/.
Hello @emceeaich,
I'm new to the codebase and I would like to give this bug a try! Should I still be going off the information in comment 4 or just comment 6?
|
|
Reporter | |
Comment 8•5 years ago
|
||
(In reply to eric from comment #7)
Hello @emceeaich,
I'm new to the codebase and I would like to give this bug a try! Should I still be going off the information in comment 4 or just comment 6?
Since this is a one-time edit, the instructions in comment 4 are fine.
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #8)
(In reply to eric from comment #7)
Hello @emceeaich,
I'm new to the codebase and I would like to give this bug a try! Should I still be going off the information in comment 4 or just comment 6?Since this is a one-time edit, the instructions in comment 4 are fine.
Which repo should I make the PR for?
|
|
Reporter | |
Comment 10•5 years ago
|
||
(In reply to eric from comment #9)
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #8)
(In reply to eric from comment #7)
Hello @emceeaich,
I'm new to the codebase and I would like to give this bug a try! Should I still be going off the information in comment 4 or just comment 6?Since this is a one-time edit, the instructions in comment 4 are fine.
Which repo should I make the PR for?
|
|
Assignee | |
Comment 11•5 years ago
|
||
Done manually.
Description
•