anthropics/claude-code-action
1
0
Fork 0
mirror of https://github.com/anthropics/claude-code-action.git synced 2026-01-22 22:44:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

Enable use_commit_signing to provide MCP file ops server for CI fixes

Browse Source 
- Add use_commit_signing: true to auto-fix workflows
- Update slash commands to use mcp__github_file_ops__commit_files
- This enables Claude to write and commit files through MCP
This commit is contained in:
km-anthropic
2025-08-19 15:14:50 -07:00
parent 4a40e4252f
commit 42fce56d3f
6 changed files with 21 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.claude/commands/fix-ci-commit.md
View File

@@ -31,20 +31,18 @@ Based on the error logs:
After fixing ALL issues, you MUST:
```bash
# Stage all changes
git add -A
Use the `mcp__github_file_ops__commit_files` tool to commit all your changes with a descriptive message like:
# Commit with descriptive message
git commit -m "Fix CI failures
```
Fix CI failures
- Fixed syntax errors
- Fixed formatting issues
- Fixed test failures
[List actual fixes made]"
[List actual fixes made]
```
**IMPORTANT**: You MUST use the Bash tool to run the git add and git commit commands above. The workflow expects you to commit your changes.
**IMPORTANT**: You MUST use the MCP file ops tool to commit your changes. The workflow expects you to commit your changes.
### 3. Verify (Optional)

10
.claude/commands/fix-ci.md
View File

@@ -42,11 +42,11 @@ Requirements:
## Step 4: Commit Changes
After applying ALL fixes, use the Bash tool to:
1. Run: `git add -A` to stage all modified files
2. Run: `git commit -m "Fix CI failures: <description>"` to commit the changes
3. Include details about which CI jobs/tests were fixed in the commit message
4. Important: You MUST use the Bash tool to run these git commands to commit your changes
After applying ALL fixes:
1. Use the `mcp__github_file_ops__commit_files` tool to commit your changes
2. Include a descriptive commit message explaining what was fixed
3. Document which CI jobs/tests were addressed in the commit message
4. Important: Use the MCP file ops tool, not git commands directly
## Step 5: Verify Fixes Locally

1
.github/workflows/auto-fix-ci-inline.yml vendored
View File

@@ -147,6 +147,7 @@ jobs:
github_token: ${{ secrets.GITHUB_TOKEN }}
timeout_minutes: "30"
use_sticky_comment: "true"
use_commit_signing: "true"
claude_args: "--max-turns 15"
- name: Push fix branch

1
.github/workflows/auto-fix-ci.yml vendored
View File

@@ -89,6 +89,7 @@ jobs:
github_token: ${{ secrets.GITHUB_TOKEN }}
timeout_minutes: "30"
use_sticky_comment: "true"
use_commit_signing: "true"
claude_args: "--max-turns 15"
- name: Push fix branch

12
slash-commands/fix-ci-commit.md
View File

@@ -31,20 +31,18 @@ Based on the error logs:
After fixing ALL issues, you MUST:
```bash
# Stage all changes
git add -A
Use the `mcp__github_file_ops__commit_files` tool to commit all your changes with a descriptive message like:
# Commit with descriptive message
git commit -m "Fix CI failures
```
Fix CI failures
- Fixed syntax errors
- Fixed formatting issues
- Fixed test failures
[List actual fixes made]"
[List actual fixes made]
```
**IMPORTANT**: You MUST use the Bash tool to run the git add and git commit commands above. The workflow expects you to commit your changes.
**IMPORTANT**: You MUST use the MCP file ops tool to commit your changes. The workflow expects you to commit your changes.
### 3. Verify (Optional)

8
slash-commands/fix-ci.md
View File

@@ -43,10 +43,10 @@ Requirements:
## Step 4: Commit Changes
After applying fixes:
1. Stage all modified files with `git add -A` or `git add .`
2. Commit with a descriptive message using `git commit -m "Fix CI failures: <description>"`
3. Include details about which CI jobs/tests were fixed in the commit message
4. Important: Always commit your changes even if you're already on a branch
1. Use the `mcp__github_file_ops__commit_files` tool to commit your changes
2. Include a descriptive commit message explaining what was fixed
3. Document which CI jobs/tests were addressed in the commit message
4. Important: Use the MCP file ops tool to commit your changes
## Step 5: Verify Fixes Locally