coverallsapp / coverallsapp/github-action
support of coveralls JSON format
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Are there plans to support the JSON format described in the API docs? This format is internal generated from the lcov info file.
E.g. gcovr can create the internal file but not the lcov info file.
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 with the linked Coveralls API documentation and compare its JSON format with the coverage input currently accepted by this GitHub Action. Check how gcovr-generated JSON is handled, and consider the work complete when that format is accepted and its behavior is covered by the relevant action tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100