Merge ~cjwatson/launchpad:shellcheck into launchpad:master
Proposed by
Colin Watson
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | cadc72c95dbad49f077180bce683e8ea26fc5e27 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/launchpad:shellcheck |
Merge into: | launchpad:master |
Diff against target: |
149 lines (+21/-11) 8 files modified
.pre-commit-config.yaml (+4/-0) cronscripts/publishing/cron.base-ppa.sh (+3/-1) cronscripts/publishing/cron.daily-ppa (+3/-2) cronscripts/publishing/cron.publish-copy-archives (+0/-2) cronscripts/publishing/cron.publish-ppa (+1/-0) utilities/launchpad-database-setup (+3/-0) utilities/rocketfuel-get (+2/-1) utilities/rocketfuel-setup (+5/-5) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jürgen Gmach | Approve | ||
Review via email:
|
Commit message
Enforce shellcheck in pre-commit
Description of the change
Fix an assorted collection of minor `shellcheck` complaints, and enforce this in `pre-commit` so that they don't come back.
To post a comment you must log in.
You have added great insight in the commit messages why we do things differently as one might expect, and especially as the linter expects.
Could you please add the reasoning also to the source code as a comment?
Probably nobody except you and maybe William would know something like "However, this structure is deliberate: we use it when migrating between PostgreSQL versions. Disable the warning."
While `git blame` makes it easy to view the current commit message, after some time and changes it is pretty cumbersome to dig out relevant information.