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

Update CI fix workflows to ensure Claude commits changes

Browse Source 
- Clarify that Claude must commit changes even when branch exists
- Update both slash command and inline workflow instructions
- Make git add and commit commands more explicit
This commit is contained in:
km-anthropic
2025-08-19 14:08:14 -07:00
parent 54d68a2a5f
commit 130eff6d9c
3 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -40,13 +40,13 @@ Requirements:
- Ensure changes are production-ready, not temporary hacks - Ensure changes are production-ready, not temporary hacks
- Preserve existing functionality while fixing issues - Preserve existing functionality while fixing issues
## Step 4: Create Branch and Commit Changes ## Step 4: Commit Changes
After applying fixes: After applying fixes:
1. Create a branch named `claude-fix-ci-${timestamp}` 1. Stage all modified files with `git add -A` or `git add .`
2. Stage all modified files with `git add` 2. Commit with a descriptive message using `git commit -m "Fix CI failures: <description>"`
3. Commit with a descriptive message explaining what was fixed 3. Include details about which CI jobs/tests were fixed in the commit message
4. Document which CI jobs/tests were addressed 4. Important: Always commit your changes even if you're already on a branch
## Step 5: Verify Fixes Locally ## Step 5: Verify Fixes Locally

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

@@ -120,12 +120,12 @@ jobs:
- Ensure changes are production-ready, not temporary hacks - Ensure changes are production-ready, not temporary hacks
- Preserve existing functionality while fixing issues - Preserve existing functionality while fixing issues
## Step 4: Create Branch and Commit Changes ## Step 4: Commit Changes
After applying fixes: After applying ALL fixes:
1. Stage all modified files with `git add` 1. Stage all modified files with `git add -A`
2. Commit with a descriptive message explaining what was fixed 2. Commit with: `git commit -m "Fix CI failures: prettier formatting and syntax errors"`
3. Document which CI jobs/tests were addressed 3. Important: You MUST commit your changes - the branch already exists
## Step 5: Verify Fixes Locally ## Step 5: Verify Fixes Locally

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

@@ -40,13 +40,13 @@ Requirements:
- Ensure changes are production-ready, not temporary hacks - Ensure changes are production-ready, not temporary hacks
- Preserve existing functionality while fixing issues - Preserve existing functionality while fixing issues
## Step 4: Create Branch and Commit Changes ## Step 4: Commit Changes
After applying fixes: After applying fixes:
1. Create a branch named `claude-fix-ci-${timestamp}` 1. Stage all modified files with `git add -A` or `git add .`
2. Stage all modified files with `git add` 2. Commit with a descriptive message using `git commit -m "Fix CI failures: <description>"`
3. Commit with a descriptive message explaining what was fixed 3. Include details about which CI jobs/tests were fixed in the commit message
4. Document which CI jobs/tests were addressed 4. Important: Always commit your changes even if you're already on a branch
## Step 5: Verify Fixes Locally ## Step 5: Verify Fixes Locally