-
Notifications
You must be signed in to change notification settings - Fork 161
50 lines (43 loc) · 1.94 KB
/
claude.yml
File metadata and controls
50 lines (43 loc) · 1.94 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
name: Claude Code
on:
issues:
types: [assigned]
jobs:
analyze:
if: github.repository == 'voidzero-dev/vite-plus' && github.event.action == 'assigned' && github.event.assignee.login == 'boshen'
runs-on: ubuntu-slim
permissions:
contents: read
issues: write
id-token: write
steps:
- name: Checkout repository
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
fetch-depth: 100
persist-credentials: true
- name: Run Claude Code
id: claude
uses: anthropics/claude-code-action@26ec041249acb0a944c0a47b6c0c13f05dbc5b44 # v1.0.70
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
assignee_trigger: 'boshen'
claude_args: --allowedTools "Edit,Write,Read,Glob,Grep,Bash(gh:*),Bash(cargo:*),Bash(git:*),Bash(just:*),WebFetch,TodoWrite"
prompt: |
Analyze issue #${{ github.event.issue.number }} in ${{ github.repository }} and determine if it can be fixed.
First, use `gh issue view ${{ github.event.issue.number }}` to read the issue details.
Then:
1. Search the codebase to gather relevant context (related files, existing implementations, tests)
2. Determine if the issue is fixable and estimate the complexity
Finally, post a comment on the issue with:
- A brief summary of your understanding of the issue
- Relevant files/code you found
- Whether this issue is fixable (yes/no/needs clarification)
- If the issue is unclear, ask for more context
- If fixable, provide a concrete implementation plan with specific steps
- Any potential concerns or blockers
- name: Unassign boshen
if: always()
env:
GH_TOKEN: ${{ github.token }}
run: gh issue edit ${{ github.event.issue.number }} --remove-assignee Boshen