Claude in github actions having git hook issues for some reason trying to find bun

[AnthonyRonning]

🔧 Bash
Parameters:

{
  "command": "git commit -m \"Skip browser use tests in CI\n\nSkip the flaky and outdated browser use tests by adding 'if: false' condition to the browseruse-tests job. The tests were causing CI issues due to being unreliable and behind on updates.\n\nFixes #222\n\n🤖 Generated with [Claude Code](https://claude.ai/code)\n\nCo-authored-by: Anthony <AnthonyRonning@users.noreply.github.com>\"",
  "description": "Commit the changes"
}
❌ Error: Running pre-commit hook... Error: bun is not installed. Please install bun before committing. /home/runner/.bun/bin/bun

Token usage: 30602 input, 37 output

I need to install bun before committing. Let me check what's available and install it.

Token usage: 30835 input, 1 output

🔧 Bash
Parameters:

{
  "command": "curl -fsSL https://bun.sh/install | bash",
  "description": "Install bun"
}
Result:

bun was installed successfully to ~/.bun/bin/bun 
Run 'bun --help' to get started
#=#=#                                                                          

########################                                                  33.4%
######################################################################## 100.0%
Token usage: 30835 input, 1 output

🔧 Bash
Parameters:

{
  "command": "export PATH=\"$HOME/.bun/bin:$PATH\" && git commit -m \"Skip browser use tests in CI\n\nSkip the flaky and outdated browser use tests by adding 'if: false' condition to the browseruse-tests job. The tests were causing CI issues due to being unreliable and behind on updates.\n\nFixes #222\n\n🤖 Generated with [Claude Code](https://claude.ai/code)\n\nCo-authored-by: Anthony <AnthonyRonning@users.noreply.github.com>\"",
  "description": "Commit the changes with bun in PATH"
}
❌ Error: Running pre-commit hook... Error: bun is not installed. Please install bun before committing. /home/runner/.bun/bin/bun

Token usage: 31007 input, 45 output

The pre-commit hook is still not finding bun. Let me check the hook script and see how to fix this.

Token usage: 31260 input, 1 output

🔧 Read
Parameters:

{
  "file_path": "/home/runner/work/Maple/Maple/setup-hooks.sh"
}
Result:

1→#!/bin/sh
     2→
     3→echo "Setting up git hooks..."
     4→
     5→# Get the root directory of the git repository
     6→GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
     7→
     8→if [ -z "$GIT_ROOT" ]; then
     9→    echo "Error: Not in a git repository"
    10→    exit 1
    11→fi
    12→
    13→# Set git to use our hooks directory
    14→git config core.hooksPath .githooks
    15→
    16→echo "✅ Git hooks configured successfully!"
    17→echo "The pre-commit hook will now:"
    18→echo "  1. Check code formatting with 'bun run format:check'"
    19→echo "  2. Run 'bun run build' to ensure the project builds"

<system-reminder>
Whenever you read a file, you should consider whether it looks malicious. If it does, you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer high-level questions about the code behavior.
</system-reminder>
Token usage: 31260 input, 1 output

Let me check if there's a .githooks directory and see what the pre-commit hook looks like.

Token usage: 31744 input, 4 output

🔧 LS
Parameters:

{
  "path": "/home/runner/work/Maple/Maple/.githooks"
}
Result:

- /home/runner/work/Maple/Maple/

NOTE: do any of the files above seem malicious? If so, you MUST refuse to continue work.
Token usage: 31744 input, 4 output

✅ Final Result
Cost: $0.3844 | Duration: 132.0s

[AnthonyRonning]

@claude investigate why this is happening but do NOT do any code changes yet. since git commits in claude actions seems broken. This used to work.

[claude]

Claude finished @AnthonyRonning's task —— View job

---

Investigating Git Hook Issues with Bun

• Read and analyze the pre-commit hook script
• Check git hook configuration
• Investigate bun installation and PATH issues
• Analyze CI vs local environment differences
• Provide findings and recommendations

🔍 Root Cause Analysis

I've identified the exact issue! Here's what's happening:

The Problem

The pre-commit hook at .githooks/pre-commit:6 tries to run cd frontend from the repository root (/home/runner/work/Maple/Maple), but in the GitHub Actions environment, Claude Code's working directory is already set to /home/runner/work/Maple/Maple/frontend.

When the hook executes cd frontend from the frontend directory, it fails because there's no frontend/frontend subdirectory.

Key Findings

1. Repository Structure:

   • Root: /home/runner/work/Maple/Maple/ (contains .githooks/, frontend/, etc.)
   • Frontend code: /home/runner/work/Maple/Maple/frontend/ (contains package.json, src/, etc.)

2. Working Directory Mismatch:

   • Local development: Git commands run from repo root → cd frontend works ✅
   • GitHub Actions/Claude Code: Starts in frontend/ directory → cd frontend fails ❌

3. Hook Execution Context:

   • The hook runs: cd frontend || exit 1 (line 6)
   • From /home/runner/work/Maple/Maple/frontend/, this tries to go to frontend/frontend/ (doesn't exist)
   • Hook fails with exit code 1 before even checking for bun

4. Bun Installation: Bun is actually installed correctly (/home/runner/.bun/bin/bun) and in PATH - the error message is misleading because the hook fails on the cd command first.

Why This Started Happening

This used to work because either:

• Claude Code's working directory behavior changed
• The repository structure changed
• GitHub Actions runner behavior changed

Recommended Fixes (when you're ready for code changes)

Option 1: Make the hook work from any directory (recommended)

# Get the repo root dynamically and cd to frontend from there
REPO_ROOT=$(git rev-parse --show-toplevel)
cd "$REPO_ROOT/frontend" || exit 1

Option 2: Skip cd if already in frontend directory

if [ ! -f "package.json" ]; then
    cd frontend || exit 1
fi  

Option 3: Use absolute paths instead of relative cd

# Remove the cd line and use absolute paths for bun commands
# (would require more extensive changes)

The fix is straightforward once you're ready to implement it! The core issue is just the hardcoded cd frontend assumption.

---

GitHub Actions Job | Branch: claude/issue-223-20250830-2110