Give `kubeflow/testing` its own PR CI
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 91
- Avg merge
- 12d 10h
- Merged PRs (30d)
- 1
Description
A few starter ideas include a self-test workflow per action, create-cluster self-test across a Kubernetes matrix, actionlint, zizmor, copyright boilerplate check, etc.
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 by reviewing the repository's existing CI configuration and the kubeflow/testing actions to determine how a dedicated PR workflow should be organized. Compare the proposed self-tests, Kubernetes matrix, actionlint, zizmor, and copyright checks, then define completion as those checks running for this repository's pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes, python
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100