actions / actions/actions-runner-controller
Separate Git repository for the chart releases
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
I don't think it's the user's fault at all but the reality is that I have been asked questions like https://github.com/actions-runner-controller/actions-runner-controller/issues/1130 several times.
That's the consequence of using chart-releaser-action (and perhaps chart-releaser) in the same repo and it can be avoided at all if we used another repository that is dedicated to the chart releases.
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 linked .github/workflows/on-push-master-publish-chart.yml workflow, especially the referenced section using chart-releaser-action, and the related issue #1130. The issue proposes a separate repository dedicated to chart releases; done means chart releases are handled from that dedicated repository rather than the controller repository, though the migration details are not specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100