Thank you for writing this! I'd been wondering if there was support for this (and shfmt come to that).
I have a .shellcheckrc in my repository root. It's not picked up; I validated this by adding --exclude=SC2086 to it and running against a file that violates that; that rule is still included.
I have copy/pasted to WORKSPACE and a BUILD file precisely as in README.md @ ceb47de.
Should I expect it to? My instinct is "not yet" as I don't see shellcheckrc appear in this repo.
Is there a way I can supply arguments to the underlying invocation of shellcheck, or a change I might patch in to have the rule look in the workspace-root for the config (as that's the most likely location)?
Thank you for writing this! I'd been wondering if there was support for this (and
shfmtcome to that).I have a
.shellcheckrcin my repository root. It's not picked up; I validated this by adding--exclude=SC2086to it and running against a file that violates that; that rule is still included.I have copy/pasted to WORKSPACE and a BUILD file precisely as in README.md @ ceb47de.
Should I expect it to? My instinct is "not yet" as I don't see
shellcheckrcappear in this repo.Is there a way I can supply arguments to the underlying invocation of shellcheck, or a change I might patch in to have the rule look in the workspace-root for the config (as that's the most likely location)?