mozilla-services / mozilla-services/updatebot
Handle merge conflict failure in db.has_job
Open
Nobody has claimed this yet.
Complicated
P4
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Somewhere around db.has_job we should see if we had a job that failed due to merge conflicts, and if the bug we filed for those merge conflicts has been closed. If it hasn't, we should assume that future jobs would also fail, and skip this library.
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 with automation.py around the linked line and inspect db.has_job to understand how job failures and library updates are represented. Trace how merge-conflict failures relate to the status of the filed bug; done means future jobs skip a library while that conflict bug remains open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100