Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(release.md): fix release process workflows explanation #745

Merged
merged 1 commit into from
Oct 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions release.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@ The automated release process starts when any modification added to `master` tri

We have two main workflows:

- [test](.github/workflows/test.yml): This will check the chart lint and will also run tests to validate if the chart can be installed, if the chart have tests those will run as well.
- [release](.github/workflows/release.yml): This will run everything a Pull Requests of a chart is merged, it will update the index and generate the package, and publish it.
- [test](.github/workflows/test.yml): This will run whenever a PR is created; it checks the chart lint and runs tests to validate if the chart can be installed; if the chart has tests, those will run as well.
- [release](.github/workflows/release.yml): This will run whenever one or more commits, referring to a chart, is/are merged into `master` (e.g.: a PR is merged); it updates the index, generates the package and publishes it.

### GitHub Pages job

Expand Down