Proposal: development scripts

[WillAbides]

I would like to add a "script" directory to make it a bit more convenient to run common development tasks. This follows the pattern of GitHub's scripts-to-rule-them-all.

The scripts would be:

• script/test runs go test ./... on all modules.
• script/generate
  • runs go generate ./... on all modules.
  • with --check validates that running script/generate produces no diff.
• script/lint
  • installs and runs golangci-lint on all modules (except newreposecretwithlibsodium)
  • runs generate --check.
• script/fmt runs go fmt ./... on all modules.

[gmlewis]

I wonder why they don't name the directory "scripts"?!?

[WillAbides]

I wonder why they don't name the directory "scripts"?!?

I asked the same question. It's been a while so I may be mixing this up with something else, but I think the original iteration had a single script with sub-commands. Kind of like "git diff" used to call a separate binary "git-diff".

[gmlewis]

OK, then let's break with tradition and start a new trend and call ours "scripts" if you don't mind. 😁

[WillAbides]

@gmlewis I just happened on to #671 and now think singular script might be the better name.

[gmlewis]

Ugh. Fine. I guess I'll have to try and change my very old habit.