CI onboarding checklist for new Kubeflow subprojects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 91
- Avg merge
- 12d 10h
- Merged PRs (30d)
- 1
Description
This is a meta-issue tracking what a new repo should have on day one, in what order, with links to the shared workflows.
The goal is for a new repo to not have to reinvent choices (runner label, e2e cluster strategy) by copying repos without a shared standard. That is the recurring cost the testing repo exists to eliminate.
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 inventorying the existing shared workflows and the CI choices currently copied across Kubeflow repositories, especially runner labels and end-to-end cluster strategy. Organize the required day-one steps in order and link each to the relevant shared workflow; done means a new subproject can follow one agreed checklist without making those choices independently.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100