blinryTIL about https://www.shellcheck.net, an open-source tool that can find bugs in your shellscripts!
… it certainly finds bugs in *my* shellscripts. /o\ #bangbangcon
Chris. R. 🎧🎼☕🍍@blinry should be the minimal check on all your shellscripts :-)
Ryan Egesdahl 
@haploc @blinry Yes, this. #BashScripting is unsafe by default, though, so you really shouldn’t be doing anything terribly complicated in it unless you really can’t depend on another language or a C compiler being available in all cases. If you need to use Bash, you should follow a rigorous set of best practices and use Shellcheck to help enforce them. Here’s a good starting set of best practices - perhaps some day I’ll get some time to write mine down. https://bertvv.github.io/cheat-sheets/Bash.html
ACG@blinry oh boy, I'm so never gonna use this on the stuff one scripted that actually works. They're cobbled together from SO posts and I don't grok the arcane details. One change and they could go kaboom
Stewart Russell
Jeroen Baert@blinry there's a handy vscode plugin for this as well!
momo@blinry
We use it at work.😀
We use it at work.😀
Daniel Bohrer@blinry oh yes. I have it set up with the vim-syntastic plugin so it can criticise every line I write instantly! :3
clonejo@clonejo I agree! :D Sometimes, I start writing a Bash script, and then just change the shebang and do it in Ruby instead. :P
dilawar@blinry pre-commit repo has a hook for it. Searches for bash files and run shellcheck before a 'git commit'.
genevieve@blinry check out shellharden too!
armin@blinry My .bashrc produces hundreds of lines of output (since years, I never really bothered).
Peter Lyons (he)@blinry shfmt is a great autoformatter too https://github.com/mvdan/sh
stew@blinry It's really fantastic, and It has LSP support if you are into that sort of thing :)
Greg Price@blinry Yeah, ShellCheck is great! Everyone writing shell scripts -- or at least shell scripts that other people will be running or contributing to -- should use it.
Robbie Coleman@blinry I owe my shell scripting knowledge to this tool! I actually enjoy when it shows me what I could do better.
Ed W8EMVSpellcheck is "written in Haskell, if you're into that sort of thing."
Another similar tool is Hadolint at
https://github.com/hadolint/hadolint
"Dockerfile linter, validate inline bash, written in Haskell"
Linters are great especially when you use them at the start of a project!
Axman6 | 🇦🇺
There Is No MagicI always use shellcheck as well, and I spend the time saved finding more subtle problems.
o Pablo Fernández@blinry `shellcheck` is a must for me plugged with ALE in Vim. Helps a lot with hair pulling mistakes for people like me not well versed in shell scripting.
George Jones 
@blinry might as well admit I'm going to keep writing .sh ...
# This is bash. Be safe out there.
set -e
set -u
Thomas@blinry after you're done fixing your scripts you can continue with your makefiles: https://github.com/mrtazz/checkmate :D
furicle@blinry yes, required!
Dominykas
last senpai@blinry we use this in our Terraform and Ansible build pipelines at work.
Intellij also recommends when you open a file with a shell script File Type (either by extension or hash bang.)
Very useful tool.
Jesper Skytte 🇩🇰@blinry Great tool - thank you for sharing! :)
floyd aka floyd_ch@blinry the coolest part is that it checks the shebang and then applies the rules accordingly, e.g. if you want bash compatibility or posix!
~n
Christian Lauf (Backupaccount)@blinry There are even Plugins for most IDEs. 😉
Garrett McCullough@blinry wow, this looks really helpful!
randi@blinry 
love this!
love this!