-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add github action for helm chart release and verify #12
Conversation
Signed-off-by: chandankumar4 <chandan.kr404@gmail.com>
17115fc
to
f24560b
Compare
Signed-off-by: chandankumar4 <chandan.kr404@gmail.com>
adc6670
to
e031465
Compare
Signed-off-by: chandankumar4 <chandan.kr404@gmail.com>
e031465
to
162fde9
Compare
.github/workflows/publish.yaml
Outdated
on: | ||
push: | ||
branches: | ||
- main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we use a tag to trigger the release? Otherwise every time there's a merge to main, it triggers a release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yaa, that can be also done btw via current way also it won't publish any release unless there is version chance in chart.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think that we can use tag
to release, as the github action(helm/chart-releaser-action) used inside workflow is itself creating release tag based on changed on main
branch and here example also suggesting to use push on main
branch
cddc1e2
to
a43a101
Compare
a43a101
to
4779d5d
Compare
Signed-off-by: chandankumar4 <chandan.kr404@gmail.com>
4779d5d
to
909d94b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Fixes: #6
Note: Have verified the helm chart release changes via github action with version 0.0.3