Skip to content

chore: skip the pre-commit guard block on GitHub Actions #604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
theCodeDrift merged 1 commit into from
Nov 2, 2026
Merged

chore: skip the pre-commit guard block on GitHub Actions #604

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions .agents/skills/worktrees-pnpm/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,19 +157,25 @@ another CI system adds that system's own marker. With Husky, run it first in
share:

```sh
guard=.agents/skills/worktrees-pnpm/scripts/refuse-main-checkout.sh
if [ ! -f "$guard" ]; then
echo "pre-commit: $guard is missing. Run pnpm install (or pnpm dotagents install) first." >&2
exit 1
# GitHub Actions skips the dotagents install (postinstall checks CI), so the
# skill's guard may be absent there; the guard exempts Actions anyway.
if [ "${GITHUB_ACTIONS:-}" != "true" ]; then
guard=.agents/skills/worktrees-pnpm/scripts/refuse-main-checkout.sh
if [ ! -f "$guard" ]; then
echo "pre-commit: $guard is missing. Run pnpm install (or pnpm dotagents install) first." >&2
exit 1
fi
sh "$guard" || exit 1
fi
sh "$guard" || exit 1
pnpm exec lint-staged
```

The `|| exit 1` is load-bearing outside Husky. Husky 9 runs a hook as `sh -e`, so a bare
`sh "$guard"` line happens to stop there, but the same two lines as a raw git hook carry on into
`lint-staged`, and its passing exit lets the refused commit through. The missing-file check
turns a bare `sh` error into one that says what to run.
turns a bare `sh` error into one that says what to run. It sits inside the `GITHUB_ACTIONS`
test because a repo that installs this skill through dotagents skips that install under CI, so on
a runner the guard may not exist, and the check would otherwise block every automated commit.

Without Husky, call it from `.git/hooks/pre-commit`, or from whatever hook manager the repo
uses. A person who really means to commit in the primary checkout runs `git commit --no-verify`.
Expand Down
14 changes: 9 additions & 5 deletions .husky/pre-commit
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,11 @@
guard=.agents/skills/worktrees-pnpm/scripts/refuse-main-checkout.sh
if [ ! -f "$guard" ]; then
echo "pre-commit: $guard is missing. Run pnpm install (or pnpm dotagents install) first." >&2
exit 1
# GitHub Actions skips the dotagents install (postinstall checks CI), so the
# skill's guard may be absent there; the guard exempts Actions anyway.
if [ "${GITHUB_ACTIONS:-}" != "true" ]; then
guard=.agents/skills/worktrees-pnpm/scripts/refuse-main-checkout.sh
if [ ! -f "$guard" ]; then
echo "pre-commit: $guard is missing. Run pnpm install (or pnpm dotagents install) first." >&2
exit 1
fi
sh "$guard" || exit 1
fi
sh "$guard" || exit 1
pnpm exec lint-staged
Loading