# Description of problem:
Today, there is no validation for 'shell' scripts (present in the form of executable binary, files ending with `.sh`, or files ending with `.sh.in`).
Ideally, if any shell script files gets modified in the patch, that particular shell script should pass 'shellcheck' test. This should be a voting job.
Ack! Extremely useful for obvious reasons (and as an aside, this is what helps me get my bash scripts working, considering my bash skills :) )
How do we want to go about this?
There is a lot of errors at the moment. Do we want to tackle it by number? Or do we want to ignore the non-serious errors so this count is more manageable?
$ find . -name '*.sh' | xargs shellcheck | grep -c 'In'
This bug is moved to https://github.com/gluster/project-infrastructure/issues/31, and will be tracked there from now on. Visit GitHub issues URL for further details