-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Enable shellcheck for contrib/ #9122
Enable shellcheck for contrib/ #9122
Conversation
humm, it would be better to enable all contrib/ files I guess. /hold |
Today we have many contributions to contrib/offline/ and some PRs contained invalid coding style for those scripts. This enables shellcheck to make such invalid coding style easily.
19fb248
to
01685ba
Compare
/hold cancel |
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
@oomichi Good idea 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, oomichi 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 |
Today we have many contributions to contrib/offline/ and some PRs contained invalid coding style for those scripts. This enables shellcheck to make such invalid coding style easily.
Today we have many contributions to contrib/offline/ and some PRs contained invalid coding style for those scripts. This enables shellcheck to make such invalid coding style easily.
Today we have many contributions to contrib/offline/ and some PRs contained invalid coding style for those scripts. This enables shellcheck to make such invalid coding style easily.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Today we have many contributions to contrib/offline/ and some PRs contained invalid coding style for those scripts.
This enables shellcheck to make such invalid coding style easily.
Does this PR introduce a user-facing change?: