Skip to content

fix: resolve ShellCheck findings in the check and its tests - #1

Merged
eskokoivula merged 1 commit into
mainfrom
fix/shellcheck-findings
Oct 7, 2026
Merged

eskokoivula merged 1 commit into
mainfrom
fix/shellcheck-findings

Conversation

@eskokoivula

Copy link
Copy Markdown
Contributor

What and why

The first CI run failed in ShellCheck before the tests ran. One finding was real: the hook-mode case-clash check parsed ls output, which unusual file names can break; it now uses a glob. The rest were intentional single quotes (a literal $) and a false positive, now annotated. Two cd calls in the tests gained an || exit 1.

How it was tested

bash tests/check-standard.test.sh: 59 passed, 0 failed (macOS bash 3.2). CI runs ShellCheck and the tests on Linux.

Checklist

  • The title follows Conventional Commits
  • No secrets, media or files over 5 MB
  • README.md and AGENTS.md still match how to install, run and test
  • DECISIONS.md has a line for any decision made here (none made)

🤖 Generated with Claude Code

The case-clash check in hook mode now walks the folder with a glob instead
of parsing ls output, so unusual file names cannot confuse it. The other
findings were intentional single quotes and a false positive, now annotated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@eskokoivula
eskokoivula merged commit 436fe52 into main Oct 7, 2026
2 checks passed
@eskokoivula
eskokoivula deleted the fix/shellcheck-findings branch October 7, 2026 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant