-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
reintroduce helm-docs step in ci #8164
Conversation
@rikatz @tao12345666333 @cpanato , looking for lgtm/approve on this. Thanks |
/triage accepted |
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
/assign @strongjz |
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
BTW putting it back in, will this still be the same problem we had before the Release process?
@tao12345666333 if the diff is not "nil", then yes |
/approve Is there a way at least of giving a more user friendly error on gh actions, asking users to run helm-docs? |
We can put an bash echo statement there for now if you like. |
I copied your attempted if condition from yesterday and put a echo statement there. Please check latest commit @rikatz |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, longwuyuan, rikatz, tao12345666333 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
helm-docs step was removed from ci.yaml so re-introducing it.
While trying to automate helm-docs in CI. But GITHUB_TOKEN failed as the committer needs to have cla-signed and GITHUB_TOKEN does not have cla-signed, and helm-docs automation requires to commit a changed /charts/ingress-nginx/README.md back into the project. Using GITHUB_TOKEN, this is the error ;
So now re-adding helm-docs step, only for verify, while we work on a better solution for helm-docs automation in CI.