Changes should be committed when checking out an existing revision
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reviewing pull request 6780 and the checkout-existing-revision flow it introduced. Trace how that flow interacts with submitting to Phab and Try; done means the revision is committed without confusing users and those other processes continue to work.
Written by the indexing model from the issue text.
Description
Following up on https://github.com/mozilla/bugbug/pull/6780, instead of explaining that, the commit should be committed since it will be less confusing.
When doing that, we need to make sure that it is accommodated with other processes, like submitting to Phab or Try.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Contributor guide
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.
More from mozilla/bugbug
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100