Define the versioning and consumption contract for shared CI
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 91
- Avg merge
- 12d 10h
- Merged PRs (30d)
- 1
Description
The goal of this issue is to define how actions and shared CI are to be pinned for reproducibility and to not break consumer repos. Also a canary consumer repo needs to be determined whose CI runs against the main branch on a schedule, so breakage is found in kubeflow/testing rather than in multiple downstream PRs.
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
The issue does not name files, tests, or an existing entry point. Start by mapping the shared CI and action consumers in this repository, then define the reproducible pinning and versioning contract and identify a canary consumer whose scheduled main-branch CI can expose breakage; done means both decisions are documented and actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100