mozilla-services / mozilla-services/updatebot
Comment on PR with coverage results
Open
Nobody has claimed this yet.
Enhancement
Medium
P3
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Adding an easy to parse chart of code coverage changes to each PR would help us keep track of these metrics now that we aren't using codecov any longer
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 does not name files, tests, or an entry point. First locate how updatebot creates or updates pull requests and how code coverage is produced; done means adding an easy-to-parse coverage-change chart to each pull request without relying on codecov.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100