mozilla-services / mozilla-services/updatebot
When re-vendoring during the two-platform mode, we don't handle the various ways vendoring can go sideways
Open
Nobody has claimed this yet.
Bug
Easy
P4
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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
The issue names re-vendoring in two-platform mode but provides no files, tests, or reproduction details. Start by locating the two-platform re-vendoring workflow and documenting how its failure paths currently behave. Done means the identified ways vendoring can fail are handled consistently and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100