Add risky observations from uplift request comments to `uplift_info` in `patchanalysis`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by locating the patchanalysis component and the code that builds uplift_info, then trace how uplift request comments are accessed. Done means risky observations from those comments are represented in uplift_info; the issue provides no file or test names, so the relevant entry points must be identified first.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Python
- Stars
- 12
- Forks
- 19
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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/libmozdata
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mozilla/libmozdata#306 ·
-
performance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mozilla/libmozdata#2 ·
-
mozilla/libmozdata#267 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mozilla/libmozdata#266 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
mozilla/libmozdata#260 ·
All issues in mozilla/libmozdata
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·