Changes should be committed when checking out an existing revision
Open
Nobody has claimed this yet.
hackbot
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
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.
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.
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.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100