Handle documentation-only changes without excluding chart files
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- helm
- Domain
- ci-cd
Research direction
Read the CI version-bump check and chart packaging configuration, including .helmignore, then compare their behavior with the related issue #839. Identify how README-only changes are classified and verify that documentation files remain in packaged chart archives. Done means documentation-only changes do not require a chart version bump and all chart files are still included.
Written by the indexing model from the issue text.
Description
CI should allow documentation-only changes to chart files without requiring chart version bumps or excluding those files from packaged charts.
The version-bump check currently treats README changes as chart changes. Adding documentation files to .helmignore avoids that check but also removes them from the packaged chart archive. Instead, CI should distinguish documentation-only changes from changes that require a version bump, while preserving all chart files in the package.
Related:
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 39
- Avg merge
- 16h 27m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from rstudio/helm
-
Workbench Job template produces invalid YAML for long working directories containing spacesMay be free again A pull request for this issue was closed without being merged. Openteam: launcher team: workbench
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug team: workbench
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug team: launcher team: workbench
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rstudio/helm#907 · 1 comment ·
Maintainers usually reply within 1 day
-
team: connect
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cpp-best-practices/project_validator#267 ·
Maintainers usually reply within 1 day
-
deploy tests
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
damodharg6/payledger#6 ·
-
who:julian
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
julian-heidt/jellyfin-media-stack#24 · 1 comment ·
-
area/ci
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
area:build bug effort:low P5 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day