Sometimes the claude code comment will not make a commit after using '@claude' in a PR, even though it thinks it did

**Describe the bug**
Seeing comments like: `Commit: 47d0420 - All changes pushed to claude/issue-3252-20250602_030540`, but then there will be no commit that has been pushed to the branch, hours after the job ended.

**To Reproduce**
This happens randomly, I would say about 10% of the time I make a comment with @claude

**Expected behavior**
I can tell that claude is fixing the issue that i said in the comment, it's just not committing the code at the end the branch

**Screenshots**
As you can see here, Claude thinks that it pushed the commit, but that commit isn't in the branch history

**Workflow yml file**

# Mock/disabled email sending in CI
RESEND_STAGING_MODE: "true"
# CI environment detection
GITHUB_ACTIONS: "true"
CI: "true"
with:
allowed_tools: "Bash,Bash(chmod:*),Bash(git:*),Bash(bun:*),Bash(bun test:*),Bash(bun run:*),Bash(bun run build),Bash(bun install),Edit,View,GlobTool,GrepTool,BatchTool,Write"
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
github_token: ${{ secrets.PAT_TOKEN }}
max_turns: "500"
timeout_minutes: "120"
custom_instructions: $(cat ABOUT_OUR_BUSINESS.md)
direct_prompt: |
Don't pipe anything, run one command at a time.

If you need to clean up a test's Supabase rows, use the existing test-utils cleanup function.

The starting state of the repo will be given to you, and your job is make it pass the tests that were made and leave our repository in the best state possible with respect to coding practices.

Start off by running a git diff with origin/main to see what the changes are and what is the motion of the current work.

Iteratively edit files and run tests again until you have tested the functionality of the new changes. Make sure that the code changes you make adhere to the guidelines in CLAUDE.md.

When implementing new features or fixes from GitHub issues (as distinct from existing pull requests), please commit your incremental progress to a dedicated feature branch and communicate the branch name in your GitHub comment for transparency and collaboration.

Before you finish making your changes, commit your current branch and then do a `bun run scripts/testing/runGithubTests.ts [current branch] main`, which runs all the tests that you need to use in parallel that are committed from the current branch, and prints out tests that are failing.

When you're finished, add, commit, and push your changes to the original branch name, and make a PR to the main branch if there isn't one already. When resolving merge conflicts, remember to force push to the current branch (but never force push to main). ALWAYS make sure you push to your branch and then make a PR to the main branch.

You can run any arbitrary bash command in the command line to help you complete your work, since we have given you permission via allowed_tools.

**API Provider**

[X] Anthropic First-Party API (default)
[ ] AWS Bedrock
[ ] GCP Vertex

**Additional context**
Add any other context about the problem here.