neuralbertatech / neuralbertatech/natKit
Make the code coverage report from the GitHub Actions more visible
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently the GitHub Actions does a code coverage report. However it is pretty hard to find and it would be nice if it was more visible, for example adding a report message to PRs automatically. Look into if this is possible and if not what things can be done to increase it's visibility.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the repository's GitHub Actions workflow that produces the code coverage report and determine where its output is currently published. Compare feasible ways to surface the report on pull requests, then document or implement the chosen approach and verify that a pull request displays an accessible coverage result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100