docs: Add prerequisite to README (#101)
This commit is contained in:
@@ -6,8 +6,10 @@ A GitHub action to turn a GitHub project into a self-hosted Helm chart repo, usi
|
|||||||
|
|
||||||
### Pre-requisites
|
### Pre-requisites
|
||||||
|
|
||||||
1. A GitHub repo containing a directory with your Helm charts (eg: `/charts`)
|
1. A GitHub repo containing a directory with your Helm charts (default is a folder named `/charts`, if you want to
|
||||||
1. A GitHub branch called `gh-pages` to store the published charts. See `charts_repo_url` for alternatives
|
maintain your charts in a different directory, you must include a `charts_dir` input in the workflow).
|
||||||
|
1. A GitHub branch called `gh-pages` to store the published charts. See `charts_repo_url` for alternatives.
|
||||||
|
1. In your repo, go to Settings/Pages. Change the `Source` `Branch` to `gh-pages`.
|
||||||
1. Create a workflow `.yml` file in your `.github/workflows` directory. An [example workflow](#example-workflow) is available below.
|
1. Create a workflow `.yml` file in your `.github/workflows` directory. An [example workflow](#example-workflow) is available below.
|
||||||
For more information, reference the GitHub Help Documentation for [Creating a workflow file](https://help.github.com/en/articles/configuring-a-workflow#creating-a-workflow-file)
|
For more information, reference the GitHub Help Documentation for [Creating a workflow file](https://help.github.com/en/articles/configuring-a-workflow#creating-a-workflow-file)
|
||||||
|
|
||||||
@@ -62,7 +64,7 @@ jobs:
|
|||||||
```
|
```
|
||||||
|
|
||||||
This uses [@helm/chart-releaser-action](https://www.github.com/helm/chart-releaser-action) to turn your GitHub project into a self-hosted Helm chart repo.
|
This uses [@helm/chart-releaser-action](https://www.github.com/helm/chart-releaser-action) to turn your GitHub project into a self-hosted Helm chart repo.
|
||||||
It does this – during every push to `main` – by checking each chart in your project, and whenever there's a new chart version, creates a corresponding [GitHub release](https://help.github.com/en/github/administering-a-repository/about-releases) named for the chart version, adds Helm chart artifacts to the release, and creates or updates an `index.yaml` file with metadata about those releases, which is then hosted on GitHub Pages
|
It does this – during every push to `main` – by checking each chart in your project, and whenever there's a new chart version, creates a corresponding [GitHub release](https://help.github.com/en/github/administering-a-repository/about-releases) named for the chart version, adds Helm chart artifacts to the release, and creates or updates an `index.yaml` file with metadata about those releases, which is then hosted on GitHub Pages. You do not need an `index.yaml` file in `main` at all because it is managed in the `gh-pages` branch.
|
||||||
|
|
||||||
#### Example using custom config
|
#### Example using custom config
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user