Add BASH Linters for CICD Code

[kj4ezj]

Following devrel issue 135, this issue has a BASH linter being added to this repo, then being set as a required check on all CICD builds. As of this writing, the only BASH script are for CICD itself but those should be checked along with any other BASH scripts added to this repo.

Automation recommends implementing both ShellCheck and bashate with the following configurations:

shellcheck -x -f gcc -S error $FILE
bashate -i E006 $FILE

The shfmt utility can be used to automatically correct some types of linter errors, similar to yarn lint --fix with eslint in JavaScript. However, it should not be used for a CICD check.

cat $FILE | shfmt -i 4 -sr -d

See Also

• devrel issue 80 - Standup DevHub Infrastructure
• devrel issue 96 - DNS Mapping for learn.eosnetwork.com
• devrel issue 134 - Update DevHub Site
• devrel issue 135 - DevHub Frontend CICD
• devrel issue 137 - Encrypt DevHub Backend
• devhub issue 12 - Put AWS Resources into Terraform with a CICD Deployment
• devhub issue 13 - Document CICD System
• devhub issue 14 - Staging Environment
• devhub issue 15 - Backend CICD
• devhub issue 16 - Structures CICD
• devhub issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
• devhub issue 18 - Add BASH Linters for CICD Code
• devhub issue 19 - Include Test Suite in CICD