WIP: fix: shellcheck assertions, POSIX compliance #101
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
actions/forgejo-release!101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "crueter/forgejo-release:shellcheck"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mostly just quoting; now shellcheck won't try to murder me everytime I
open this file
For POSIX compliance, moved some
[[to[(maintaining proper null checks). Also useset --for the asset array, and prefercommand -voverwhich.Signed-off-by: crueter crueter@eden-emu.dev
fix: all shellcheck assertionsto fix: shellcheck assertions, POSIX compliance@ -52,3 +52,3 @@local sha=$(jq --raw-output .commit.sha <"$TAG_FILE")sha=$(jq --raw-output .commit.sha <"$TAG_FILE")test "$sha" = "$SHA"elsewhy local removal? now sha will propagate to caller
localis not POSIX compliant. If there's a conflcting variable in a caller we can rename this.@ -113,3 +116,3 @@local id=$(api GET repos/$REPO/releases/tags/"$TAG_URL" | jq --raw-output .id)id=$(api GET "repos/$REPO/releases/tags/$TAG_URL" | jq --raw-output .id)same here?
btw: this is not enough
shell: bash@viceice wrote in #101 (comment):
Wdym? We can change this to sh without issue
EDIT: nvm I see now
I have no idea why integrations is failing. That log is impossible to read.
fix: shellcheck assertions, POSIX complianceto WIP: fix: shellcheck assertions, POSIX complianceView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.