Refactor issue workflows for improved automation
- Consolidate issue-triage.yml and issue-deduplication.yml into single workflow with sequential jobs - Create daily_issue_maintenance.yml with three jobs: - find-legacy-duplicates: Manual job to scan all open issues for duplicates - check-stale-issues: Daily job to request confirmation on issues >60 days old - close-unconfirmed-issues: Daily job to close issues without confirmation after 14 days - Update triage to use gh CLI tools with database-specific labels (neo4j, falkordb, neptune) - Separate deduplication into dedicated job using MCP GitHub tools - Add "duplicate" label to both real-time and batch deduplication workflows - Update claude-code-review.yml to use latest Sonnet model 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Daniel Chalef
parent
a24ada94bb
commit
fc58545751
3 changed files with 264 additions and 0 deletions
1
.github/workflows/claude-code-review.yml
vendored
1
.github/workflows/claude-code-review.yml
vendored
|
|
@ -50,3 +50,4 @@ jobs:
|
|||
|
||||
claude_args: |
|
||||
--allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*)"
|
||||
--model claude-sonnet-4-5-20250929
|
||||
|
|
|
|||
123
.github/workflows/daily_issue_maintenance.yml
vendored
Normal file
123
.github/workflows/daily_issue_maintenance.yml
vendored
Normal file
|
|
@ -0,0 +1,123 @@
|
|||
name: Daily Issue Maintenance
|
||||
on:
|
||||
schedule:
|
||||
- cron: "0 0 * * *" # Every day at midnight
|
||||
workflow_dispatch: # Manual trigger option
|
||||
|
||||
jobs:
|
||||
find-legacy-duplicates:
|
||||
runs-on: ubuntu-latest
|
||||
if: github.event_name == 'workflow_dispatch'
|
||||
permissions:
|
||||
contents: read
|
||||
issues: write
|
||||
id-token: write
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 1
|
||||
|
||||
- uses: anthropics/claude-code-action@v1
|
||||
with:
|
||||
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
||||
prompt: |
|
||||
REPO: ${{ github.repository }}
|
||||
|
||||
Find potential duplicate issues in the repository:
|
||||
|
||||
1. Use `gh issue list --state open --limit 1000 --json number,title,body,createdAt` to get all open issues
|
||||
2. For each issue, search for potential duplicates using `gh search issues` with keywords from the title and body
|
||||
3. Compare issues to identify true duplicates using these criteria:
|
||||
- Same bug or error being reported
|
||||
- Same feature request (even if worded differently)
|
||||
- Same question being asked
|
||||
- Issues describing the same root problem
|
||||
|
||||
For each duplicate found:
|
||||
- Add a comment linking to the original issue
|
||||
- Apply the "duplicate" label using `gh issue edit`
|
||||
- Be polite and explain why it's a duplicate
|
||||
|
||||
Focus on finding true duplicates, not just similar issues.
|
||||
|
||||
claude_args: |
|
||||
--allowedTools "Bash(gh issue:*),Bash(gh search:*)"
|
||||
--model claude-sonnet-4-5-20250929
|
||||
|
||||
check-stale-issues:
|
||||
runs-on: ubuntu-latest
|
||||
if: github.event_name == 'schedule'
|
||||
permissions:
|
||||
contents: read
|
||||
issues: write
|
||||
id-token: write
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 1
|
||||
|
||||
- uses: anthropics/claude-code-action@v1
|
||||
with:
|
||||
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
||||
prompt: |
|
||||
REPO: ${{ github.repository }}
|
||||
|
||||
Review stale issues and request confirmation:
|
||||
|
||||
1. Use `gh issue list --state open --limit 1000 --json number,title,updatedAt,comments` to get all open issues
|
||||
2. Identify issues that are:
|
||||
- Older than 60 days (based on updatedAt)
|
||||
- Have no comments with "stale-check" label
|
||||
- Are not labeled as "enhancement" or "documentation"
|
||||
3. For each stale issue:
|
||||
- Add a polite comment asking the issue originator if this is still relevant
|
||||
- Apply a "stale-check" label to track that we've asked
|
||||
- Use format: "@{author} Is this still an issue? Please confirm within 14 days or this issue will be closed."
|
||||
|
||||
Use:
|
||||
- `gh issue view` to check issue details and labels
|
||||
- `gh issue comment` to add comments
|
||||
- `gh issue edit` to add the "stale-check" label
|
||||
|
||||
claude_args: |
|
||||
--allowedTools "Bash(gh issue:*)"
|
||||
--model claude-sonnet-4-5-20250929
|
||||
|
||||
close-unconfirmed-issues:
|
||||
runs-on: ubuntu-latest
|
||||
if: github.event_name == 'schedule'
|
||||
needs: check-stale-issues
|
||||
permissions:
|
||||
contents: read
|
||||
issues: write
|
||||
id-token: write
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 1
|
||||
|
||||
- uses: anthropics/claude-code-action@v1
|
||||
with:
|
||||
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
||||
prompt: |
|
||||
REPO: ${{ github.repository }}
|
||||
|
||||
Close unconfirmed stale issues:
|
||||
|
||||
1. Use `gh issue list --state open --label "stale-check" --limit 1000 --json number,title,comments,updatedAt` to get issues with stale-check label
|
||||
2. For each issue, check if:
|
||||
- The "stale-check" comment was added 14+ days ago
|
||||
- There has been no response from the issue author or activity since the comment
|
||||
3. For issues meeting the criteria:
|
||||
- Add a polite closing comment
|
||||
- Close the issue using `gh issue close`
|
||||
- Use format: "Closing due to inactivity. Feel free to reopen if this is still relevant."
|
||||
|
||||
Use:
|
||||
- `gh issue view` to check issue comments and activity
|
||||
- `gh issue comment` to add closing comment
|
||||
- `gh issue close` to close the issue
|
||||
|
||||
claude_args: |
|
||||
--allowedTools "Bash(gh issue:*)"
|
||||
--model claude-sonnet-4-5-20250929
|
||||
140
.github/workflows/issue-triage.yml
vendored
Normal file
140
.github/workflows/issue-triage.yml
vendored
Normal file
|
|
@ -0,0 +1,140 @@
|
|||
name: Issue Triage and Deduplication
|
||||
on:
|
||||
issues:
|
||||
types: [opened]
|
||||
|
||||
jobs:
|
||||
triage:
|
||||
runs-on: ubuntu-latest
|
||||
timeout-minutes: 10
|
||||
permissions:
|
||||
contents: read
|
||||
issues: write
|
||||
id-token: write
|
||||
|
||||
steps:
|
||||
- name: Checkout repository
|
||||
uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 1
|
||||
|
||||
- name: Run Claude Code for Issue Triage
|
||||
uses: anthropics/claude-code-action@v1
|
||||
with:
|
||||
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
||||
allowed_non_write_users: "*"
|
||||
github_token: ${{ secrets.GITHUB_TOKEN }}
|
||||
prompt: |
|
||||
You're an issue triage assistant for GitHub issues. Your task is to analyze the issue and select appropriate labels from the provided list.
|
||||
|
||||
IMPORTANT: Don't post any comments or messages to the issue. Your only action should be to apply labels. DO NOT check for duplicates - that's handled by a separate job.
|
||||
|
||||
Issue Information:
|
||||
- REPO: ${{ github.repository }}
|
||||
- ISSUE_NUMBER: ${{ github.event.issue.number }}
|
||||
|
||||
TASK OVERVIEW:
|
||||
|
||||
1. First, fetch the list of labels available in this repository by running: `gh label list`. Run exactly this command with nothing else.
|
||||
|
||||
2. Next, use gh commands to get context about the issue:
|
||||
- Use `gh issue view ${{ github.event.issue.number }}` to retrieve the current issue's details
|
||||
- Use `gh search issues` to find similar issues that might provide context for proper categorization
|
||||
- You have access to these Bash commands:
|
||||
- Bash(gh label list:*) - to get available labels
|
||||
- Bash(gh issue view:*) - to view issue details
|
||||
- Bash(gh issue edit:*) - to apply labels to the issue
|
||||
- Bash(gh search:*) - to search for similar issues
|
||||
|
||||
3. Analyze the issue content, considering:
|
||||
- The issue title and description
|
||||
- The type of issue (bug report, feature request, question, etc.)
|
||||
- Technical areas mentioned
|
||||
- Database mentions (neo4j, falkordb, neptune, etc.)
|
||||
- LLM providers mentioned (openai, anthropic, gemini, groq, etc.)
|
||||
- Components affected (embeddings, search, prompts, server, mcp, etc.)
|
||||
|
||||
4. Select appropriate labels from the available labels list:
|
||||
- Choose labels that accurately reflect the issue's nature
|
||||
- Be specific but comprehensive
|
||||
- Add database-specific labels if mentioned: neo4j, falkordb, neptune
|
||||
- Add component labels if applicable
|
||||
- DO NOT add priority labels (P1, P2, P3)
|
||||
- DO NOT add duplicate label - that's handled by the deduplication job
|
||||
|
||||
5. Apply the selected labels:
|
||||
- Use `gh issue edit ${{ github.event.issue.number }} --add-label "label1,label2,label3"` to apply your selected labels
|
||||
- DO NOT post any comments explaining your decision
|
||||
- DO NOT communicate directly with users
|
||||
- If no labels are clearly applicable, do not apply any labels
|
||||
|
||||
IMPORTANT GUIDELINES:
|
||||
- Be thorough in your analysis
|
||||
- Only select labels from the provided list
|
||||
- DO NOT post any comments to the issue
|
||||
- Your ONLY action should be to apply labels using gh issue edit
|
||||
- It's okay to not add any labels if none are clearly applicable
|
||||
- DO NOT check for duplicates
|
||||
|
||||
claude_args: |
|
||||
--allowedTools "Bash(gh label list:*),Bash(gh issue view:*),Bash(gh issue edit:*),Bash(gh search:*)"
|
||||
--model claude-sonnet-4-5-20250929
|
||||
|
||||
deduplicate:
|
||||
runs-on: ubuntu-latest
|
||||
timeout-minutes: 10
|
||||
needs: triage
|
||||
permissions:
|
||||
contents: read
|
||||
issues: write
|
||||
id-token: write
|
||||
|
||||
steps:
|
||||
- name: Checkout repository
|
||||
uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 1
|
||||
|
||||
- name: Check for duplicate issues
|
||||
uses: anthropics/claude-code-action@v1
|
||||
with:
|
||||
prompt: |
|
||||
Analyze this new issue and check if it's a duplicate of existing issues in the repository.
|
||||
|
||||
Issue: #${{ github.event.issue.number }}
|
||||
Repository: ${{ github.repository }}
|
||||
|
||||
Your task:
|
||||
1. Use mcp__github__get_issue to get details of the current issue (#${{ github.event.issue.number }})
|
||||
2. Search for similar existing OPEN issues using mcp__github__search_issues with relevant keywords from the issue title and body
|
||||
3. Compare the new issue with existing ones to identify potential duplicates
|
||||
|
||||
Criteria for duplicates:
|
||||
- Same bug or error being reported
|
||||
- Same feature request (even if worded differently)
|
||||
- Same question being asked
|
||||
- Issues describing the same root problem
|
||||
|
||||
If you find duplicates:
|
||||
- Add a comment on the new issue linking to the original issue(s)
|
||||
- Apply the "duplicate" label to the new issue
|
||||
- Be polite and explain why it's a duplicate
|
||||
- Suggest the user follow the original issue for updates
|
||||
|
||||
If it's NOT a duplicate:
|
||||
- Don't add any comments
|
||||
- Don't modify labels
|
||||
|
||||
Use these tools:
|
||||
- mcp__github__get_issue: Get issue details
|
||||
- mcp__github__search_issues: Search for similar issues (use state:open)
|
||||
- mcp__github__list_issues: List recent issues if needed
|
||||
- mcp__github__create_issue_comment: Add a comment if duplicate found
|
||||
- mcp__github__update_issue: Add "duplicate" label
|
||||
|
||||
Be thorough but efficient. Focus on finding true duplicates, not just similar issues.
|
||||
|
||||
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
|
||||
claude_args: |
|
||||
--allowedTools "mcp__github__get_issue,mcp__github__search_issues,mcp__github__list_issues,mcp__github__create_issue_comment,mcp__github__update_issue,mcp__github__get_issue_comments"
|
||||
--model claude-sonnet-4-5-20250929
|
||||
Loading…
Add table
Reference in a new issue