reenable coverage in PRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- ci-cd, testing-qa
Research direction
Start by reviewing issue #534, where the coverage functionality was removed, and inspect the repository's current PR checks. Determine how coverage was previously reported and restore that PR behavior; done means coverage is enabled and visible for pull requests.
Written by the indexing model from the issue text.
Description
Removed in #534.
- Dominant language
- Python
- Stars
- 5
- Forks
- 39
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 6
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-releng/scriptworker
-
Dependency Dashboard Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
mozilla-releng/scriptworker#748 ·
-
mozilla-releng/scriptworker#645 · 4 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
mozilla-releng/scriptworker#584 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mozilla-releng/scriptworker#580 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mozilla-releng/scriptworker#570 ·
All issues in mozilla-releng/scriptworker
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