-
Notifications
You must be signed in to change notification settings - Fork 64
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 shell linter github action #274
Conversation
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.
Thanks for your PR! 😍
Please take a look at my comment, about the scope of the linter.
Adding a hold until we are sure it's safe to adopt it
/hold
Update Linter so it works with the current opened PR Co-authored-by: Chris Suszynski <krzysztof.suszynski@gmail.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kauana The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
14c2d04
to
340de37
Compare
Hey there, sorry for this hanging here for so long. I think the correct solution is to add hack repo to knobots to use the style directive. That way the workflow is managed by the automation system. There is examples of the style reusable action in serving, eventing, etc. that uses this system. |
Hey @kvmware, sorry for the wait as well! I believe If that's ok with you, I'm happy to update that so |
That should work thanks |
- See `knative/hack` [PR](knative/hack#274 (comment))
* Include knative/hack repo for GH actions - See `knative/hack` [PR](knative/hack#274 (comment)) * Only add style action to knative/hack * Update README to reflect workflow-template changes
Changes
/kind enhancement
Fixes #269