Upload code coverage to coveralls
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 7
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 5
Description
plone.meta initially supported uploading code coverage reports to Coveralls.
Before shared workflows were introduced, there were references to Coveralls here.
We could reintroduce this optional feature in two different ways:
- In tox.ini, by adding Coveralls to [testenv:coverage]
- In the composite action
.github/workflows/coverage.yml, by adding a flag and a step to upload the coverage report
I think the second option is cleaner, since we generally only want to upload coverage reports when code is pushed.
What do you think? I’d be happy to open a pull request if there’s interest in bringing this back.
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
Read .github/workflows/coverage.yml and tox.ini, then compare the historical Coveralls reference linked in the issue. Decide which workflow approach fits the repository's shared-workflow setup and confirm that the optional upload runs for pushed code without affecting ordinary coverage runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100