chore(husky): fixed husky commit message from bash/zsh syntax to sh syntax

[MagicLegend]

Description

• Fixes Husky commit msg not compatible with /bin/sh #2570

Fixed husky commit message from bash/zsh syntax to sh syntax to match shebang

How Has This Been Tested?

Before this change:

± % git commit
✔ Preparing lint-staged...
✔ Running tasks for staged files...
✔ Applying modifications from tasks...
✔ Cleaning up temporary files...
cz-cli@4.3.1, cz-conventional-changelog@3.3.0

? Select the type of change that you're committing: style:    Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
? What is the scope of this change (e.g. component or file name): (press enter to skip) tvdb
? Write a short, imperative tense description of the change (max 87 chars):
 (76) improved logging in case of a failure to enrich the TMDB show with TVDB data
? Provide a longer description of the change: (press enter to skip)

? Are there any breaking changes? No
? Does this change affect any open issues? Yes
? If issues are closed, the commit requires a body. Please enter a longer description of the commit itself:
 Improved logging in case of a failure to enrich the TMDB show with TVDB data
? Add issue references (e.g. "fix #123", "re #123".):
 Resolves #2511
.husky/commit-msg: 4: [[: not found
[improve-tvdb-tmdb-mismatch-logging 3d3a8d74] style(tvdb): improved logging in case of a failure to enrich the TMDB show with TVDB data
 1 file changed, 1 insertion(+), 1 deletion(-)

After this change committing no longer throws the error:

± % git commit
→ No staged files match any configured task.
cz-cli@4.3.1, cz-conventional-changelog@3.3.0

? Select the type of change that you're committing: fix:      A bug fix
? What is the scope of this change (e.g. component or file name): (press enter to skip) husky
? Write a short, imperative tense description of the change (max 88 chars):
 (60) fixed husky commit message from bash/zsh syntax to sh syntax
? Provide a longer description of the change: (press enter to skip)
 Fixed husky commit message from bash/zsh syntax to sh syntax to match shebang
? Are there any breaking changes? No                                                                                                                                                                                                                                                                                          ? Does this change affect any open issues? Yes
? Add issue references (e.g. "fix #123", "re #123".):
 fixes #2570
[fix-husky-commit-msg-syntax 522016b5] fix(husky): fixed husky commit message from bash/zsh syntax to sh syntax
 1 file changed, 1 insertion(+), 1 deletion(-)

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Bug Fixes
  • Enhanced commit message validation to more reliably handle edge cases and improve robustness of variable checks.

[coderabbitai]

📝 Walkthrough

Walkthrough

The .husky/commit-msg script was updated to replace bash-specific conditional syntax with POSIX-compliant shell syntax, changing [[ -n $HUSKY_BYPASS ]] to [ -n "$HUSKY_BYPASS" ]. This resolves compatibility issues with /bin/sh environments while preserving existing behavior.

Changes

Cohort / File(s)	Summary
Shell Script Compatibility Fix .husky/commit-msg	Changed bash test syntax [[...]] to POSIX-compliant single bracket [...] with quoted variable to ensure /bin/sh compatibility and safe variable handling.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A bracket here, a quote right there,
The shell now works with extra care,
No bash-isms shall block the way,
POSIX rules the commit today! ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The pull request fully resolves issue #2570 by changing [[ to [ syntax for POSIX sh compatibility. Issues #123 and #2511 are unrelated to this pull request.
Out of Scope Changes check	✅ Passed	The single change to .husky/commit-msg is directly in scope for fixing the POSIX sh compatibility issue (#2570); no out-of-scope changes detected.
Title check	✅ Passed	The PR title accurately summarizes the main change: fixing the .husky/commit-msg script from bash/zsh syntax to POSIX sh syntax, which is the core objective addressed by the changeset.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fallenbagel]

As mentioned in the issue. This is not a bug so this shouldnt be labelled "fix". A bug is a bug in the application. This is not related to the application.

This should be a chore.

[coderabbitai]

🧹 Nitpick comments (1)

.husky/commit-msg (1)

4-4: Quote $1 to avoid word-splitting.

This is usually safe, but quoting makes the hook robust if the commit message path ever contains spaces.

Suggested change

-[ -n "$HUSKY_BYPASS" ] || npx commitlint --edit $1
+[ -n "$HUSKY_BYPASS" ] || npx commitlint --edit "$1"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.husky/commit-msg at line 4, The hook uses an unquoted shell parameter $1
which can undergo word-splitting; update the commit hook invocation so the
commit message path is quoted by replacing npx commitlint --edit $1 with npx
commitlint --edit "$1" and keep the HUSKY_BYPASS check ([ -n "$HUSKY_BYPASS" ]
|| ...) intact; this ensures robustness when the commit message path contains
spaces without changing the existing logic that checks HUSKY_BYPASS.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.husky/commit-msg:
- Line 4: The hook uses an unquoted shell parameter $1 which can undergo
word-splitting; update the commit hook invocation so the commit message path is
quoted by replacing npx commitlint --edit $1 with npx commitlint --edit "$1" and
keep the HUSKY_BYPASS check ([ -n "$HUSKY_BYPASS" ] || ...) intact; this ensures
robustness when the commit message path contains spaces without changing the
existing logic that checks HUSKY_BYPASS.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd8b386 and 5b2d19e.

📒 Files selected for processing (1)

• .husky/commit-msg

[Copilot]

Pull request overview

This PR fixes a shell script compatibility issue in the husky commit-msg hook where bash/zsh-specific syntax was used with a POSIX sh shebang, causing errors on systems where /bin/sh is not bash or zsh.

Changes:

• Changed double bracket test [[ -n $HUSKY_BYPASS ]] to POSIX-compatible single bracket test [ -n "$HUSKY_BYPASS" ] with proper variable quoting

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[0xSysR3ll]

LGTM !