coverallsapp / coverallsapp/github-action
PR check should report coverage change between the two branches
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
When I have a PR into the master branch, the GitHub check does not report the coverage change between master and current feature branch. It reports the change from the previous commit in the current branch. It can even result in a decrease when in reality may be a huge increase in coverage for the master branch when merged.
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
Start by tracing how the GitHub check compares coverage for a pull request into master, focusing on why it uses the previous commit on the feature branch. Done means the check reports the coverage change between master and the current feature branch, including cases where the resulting change is an increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100