-
Notifications
You must be signed in to change notification settings - Fork 43
add fix-ci-failed claude code custom command #7815
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.
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| Please analyze and fix the GitHub CI job issue for a given branch. | ||
|
|
||
| Follow these steps: | ||
|
|
||
| 1. Use this shell script to pull the failed logs from the Github CI job. The first argument to the script should be the current checked out branch, which you can retrieve using the shell command `git rev-parse --abbrev-ref HEAD`. | ||
|
|
||
| ```bash | ||
| BRANCH=$1 | ||
| RUN_ID=$(gh run list --branch $BRANCH -w CI --json databaseId,conclusion,status --jq '.[0] | select(.conclusion=="failure") | .databaseId') | ||
|
|
||
| JOB_ID=$( gh run view $RUN_ID --json jobs --jq '.jobs[] | select(.conclusion=="failure") | .databaseId') | ||
|
|
||
| gh run view -v --log-failed --job $JOB_ID | ||
| ``` | ||
|
Check failure on line 14 in .claude/commands/fix-ci-failed.md
|
||
| 2. Understand the problem described in the logs | ||
|
Check failure on line 15 in .claude/commands/fix-ci-failed.md
|
||
coderabbitai[bot] marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| 3. Search the codebase for relevant files | ||
| 4. Come up with a plan first and ask for my review | ||
| 5. Implement the necessary changes to fix the issue | ||
| 6. Run tests to verify the fix | ||
| 7. Ensure code passes linting and type checking | ||
|
|
||
| Remember to use the GitHub CLI (gh) for all GitHub-related tasks. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.