Workspace: Discard-Changes guard should be aware of the Create→Edit transition #181
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
| name: Issue Deduplication | |
| on: | |
| issues: | |
| types: [ opened ] | |
| workflow_dispatch: | |
| inputs: | |
| issue_number: | |
| description: 'Issue number to analyze for duplicates' | |
| required: true | |
| type: number | |
| jobs: | |
| deduplicate: | |
| runs-on: ubuntu-latest | |
| timeout-minutes: 10 | |
| permissions: | |
| contents: read | |
| issues: write | |
| id-token: write | |
| steps: | |
| - name: Checkout repository | |
| uses: actions/checkout@v6 | |
| 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 || inputs.issue_number }} | |
| Repository: ${{ github.repository }} | |
| Your task: | |
| 1. Use mcp__github__get_issue to get details of the current issue (#${{ github.event.issue.number || inputs.issue_number }}) | |
| 2. Search for similar existing 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" and "state/needs-investigation" labels 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 | |
| - You may apply appropriate topic labels based on the issue content | |
| Use these tools: | |
| - mcp__github__get_issue: Get issue details | |
| - mcp__github__search_issues: Search for similar issues | |
| - mcp__github__list_issues: List recent issues if needed | |
| - mcp__github__add_issue_comment: Add a comment if duplicate found | |
| - mcp__github__update_issue: Add labels | |
| Be thorough but efficient. Focus on finding true duplicates, not just similar issues. | |
| anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY_03 }} | |
| # Issues are opened by community members without write access, so the | |
| # default OIDC token exchange fails with "User does not have write | |
| # access on this repository". Pass `github_token` explicitly and set | |
| # `allowed_non_write_users` to bypass that check. Safe here because | |
| # `permissions:` and `--allowedTools` below are tightly scoped to | |
| # issue operations only. | |
| github_token: ${{ secrets.GITHUB_TOKEN }} | |
| allowed_non_write_users: "*" | |
| # Surface full SDK output (including tool calls and permission denials) | |
| # to diagnose why Claude sometimes only partially completes (e.g. labels | |
| # an issue but skips the comment). Safe to leave on — no secrets in output. | |
| show_full_output: true | |
| claude_args: | | |
| --model claude-haiku-4-5 --allowedTools "mcp__github__get_issue,mcp__github__search_issues,mcp__github__list_issues,mcp__github__add_issue_comment,mcp__github__update_issue,mcp__github__get_issue_comments" |