Add CI protection for `ci/` values files that do not end in `-values.yaml`
Open
Nobody has claimed this yet.
ci
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
If they do not end in -values.yaml, they will get ignored... we should make this a CI failure case unless explicitly ignored somehow (otherwise we might think that values files are being tested when they are not)
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 locating the repository's CI configuration and the ci/ values files referenced in the issue. Check how filenames are currently selected, then define the failure and explicit-ignore behavior. Done means incorrectly named values files fail CI while allowed files continue to be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100