Suggest Uplifts
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by reviewing the existing update workflow, then define how upstream patches are scanned for security concerns and how an uplift recommendation or attempt is produced; done requires agreed behavior and corresponding validation.
Written by the indexing model from the issue text.
Description
There's been situations where a library update contains a security fix we want to uplift. We should try to scan the upstream patches for security concerns and either recommend an uplift or just try to do it ourselves.
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
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-services/updatebot
-
Easy Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mozilla-services/updatebot#401 ·
-
Easy Enhancement
Difficulty 1/5 Under an hour Newbie friendliness 65/100
mozilla-services/updatebot#348 ·
-
Bug Easy
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mozilla-services/updatebot#314 ·
-
Bug Easy
Difficulty 4/5 3-5 days Newbie friendliness 45/100
mozilla-services/updatebot#422 · 2 comments ·
-
Enhancement Medium
Difficulty 3/5 1-2 days Newbie friendliness 52/100
mozilla-services/updatebot#419 ·
All issues in mozilla-services/updatebot
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