Better CI Coverage
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 1
- Forks
- 2
- Avg merge
- 22m
- Merged PRs (30d)
- 4
Description
Not sure where to put this yet, but our CI should be testing:
- Different compilers
- Debug vs Release
- Operating systems?
- Different process/thread counts
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
No CI files, tests, or entry points are named. Start by locating the repository's current CI configuration and documenting its existing compiler, build-type, operating-system, and process/thread coverage; done means the desired coverage is defined and implemented across the relevant matrix.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100