For every PR impacting the helm chart, a linter will make sure that the change passes linting which includes forcing a version bump on changes)
For every PR impacting the helm chart, a 'kubernetes in docker' (KIND) cluster will be temporarily created and the chart will be installed to that test cluster to ensure that it installs properly
For every merge to master impacting the helm chart, automation will package the chart, update the index.yaml on the gh-pages branch, and cut a github release with the packaged chart for reference as a chart repository.
This PR should add the necessary github actions to lint, test, and release charts as they are added and changed. This is part of the solve for https://github.com/blakeblackshear/frigate/issues/156
index.yaml
on thegh-pages
branch, and cut a github release with the packaged chart for reference as a chart repository.This also assumes that the gh-pages for the repo will be published to https://blakeblackshear.github.io/blakeshome-charts - if it should be different, we will need to update
release.yaml
as appropriate.ACTION REQUIRED:
gh-pages
branch