oskoperator / oskoperator/osko
No CI workflow runs the test suite
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 3
- Avg merge
- 44m
- Merged PRs (30d)
- 7
Description
.github/workflows/ contains build-image.yaml, publish-helm-chart.yaml and release-drafter.yml. None run go test. Correctness depends entirely on contributors remembering make test locally.
The whole-branch review of #151 identified this as the reason a Critical upgrade bug — a Datasource with spec.type omitted produced no rules at all, not even the PrometheusRule — survived six per-task reviews and was only caught at final review.
Needs a workflow running make test on pull requests. Note the suite requires KUBEBUILDER_ASSETS, provided by setup-envtest.
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 in .github/workflows/ alongside build-image.yaml, publish-helm-chart.yaml, and release-drafter.yml. Add a pull-request workflow that runs make test with setup-envtest providing KUBEBUILDER_ASSETS; done means the suite runs automatically and reports failures on pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100