graph TD
    A[New Issue Created] --> B[Automated Labels]
    B --> C{Triage Review}
    C -->|Bug| D[Add bug label]
    C -->|Feature| E[Add enhancement label]
    C -->|Question| F[Add question label]
    C -->|Duplicate| G[Close as duplicate]
    D --> H[Assign to team]
    E --> H
    F --> I[Request clarification]
    H --> J[Set priority]
    J --> K[Add to milestone]

## Issue Quality Criteria

- [ ] Clear, descriptive title
- [ ] Detailed description of problem/request
- [ ] Steps to reproduce (for bugs)
- [ ] Expected vs actual behavior (for bugs)
- [ ] Environment details (OS, version, etc.)
- [ ] Relevant logs or screenshots attached
- [ ] Reproduction repository (if applicable)
- [ ] Related issues referenced
- [ ] Appropriate labels applied
- [ ] Assignee or team identified

# Search for duplicates before closing
gh issue list --search "error message" --state all

# Comment when marking as duplicate
gh issue comment 123 --body "Closing as duplicate of #45. Please continue discussion there."

# Close as duplicate
gh issue close 123 --comment "Closing as duplicate of #45" --duplicate

# .github/labels.yml
labels:
  # Type labels
  - name: "type: bug"
    color: "d73a4a"
    description: "Something isn't working"
  - name: "type: enhancement"
    color: "a2eeef"
    description: "New feature or request"
  - name: "type: documentation"
    color: "0075ca"
    description: "Improvements or additions to documentation"
  - name: "type: question"
    color: "fbca04"
    description: "Question from user"

  # Priority labels
  - name: "priority: critical"
    color: "b60205"
    description: "Critical issue, fix immediately"
  - name: "priority: high"
    color: "e99695"
    description: "High priority"
  - name: "priority: medium"
    color: "fbca04"
    description: "Medium priority"
  - name: "priority: low"
    color: "c2e0c6"
    description: "Low priority"

  # Status labels
  - name: "status: needs-triage"
    color: "bfd4f2"
    description: "Needs triage"
  - name: "status: in-progress"
    color: "0e8a16"
    description: "Currently being worked on"
  - name: "status: blocked"
    color: "5319e7"
    description: "Blocked by another issue"
  - name: "status: wontfix"
    color: "ffffff"
    description: "Will not be fixed"

  # Component labels
  - name: "component: api"
    color: "006b75"
    description: "API related"
  - name: "component: ui"
    color: "006b75"
    description: "UI related"
  - name: "component: database"
    color: "006b75"
    description: "Database related"

# .github/labeler.yml
labels:
  - name: "area: api"
    files:
      - "src/api/**"
  - name: "area: frontend"
    files:
      - "src/frontend/**"
  - name: "area: database"
    files:
      - "migrations/**"
      - "models/**"
  - name: "type: tests"
    files:
      - "**/*test*"
      - "**/*spec*"

# .github/workflows/triage.yml
name: Issue Triage

on:
  issues:
    types: [opened, reopened, labeled]

jobs:
  auto-assign:
    runs-on: ubuntu-latest
    steps:
      - name: Auto-assign based on labels
        uses: actions/github-script@v6
        with:
          script: |
            const labels = context.payload.issue.labels.map(l => l.name);
            if (labels.includes('component: api')) {
              await github.rest.issues.addAssignees({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: context.issue.number,
                assignees: ['api-team']
              });
            }

  add-needs-info-label:
    runs-on: ubuntu-latest
    if: github.event.action == 'opened'
    steps:
      - name: Check issue quality
        uses: actions/github-script@v6
        with:
          script: |
            const body = context.payload.issue.body;
            const hasSteps = body.includes('Steps to reproduce');
            const hasEnvironment = body.includes('Environment');
            if (!hasSteps || !hasEnvironment) {
              await github.rest.issues.addLabels({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: context.issue.number,
                labels: ['status: needs-info']
              });
            }

# .github/ISSUE_TEMPLATE/bug_report.md
---
name: Bug report
about: Create a report to help us improve
title: '[BUG] '
labels: 'type: bug, status: needs-triage'
assignees: ''
---

## Describe the bug
A clear and concise description of what the bug is.

## To Reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## Expected behavior
A clear and concise description of what you expected to happen.

## Screenshots
If applicable, add screenshots to help explain your problem.

## Environment
 - OS: [e.g. iOS]
 - Browser: [e.g. chrome, safari]
 - Version: [e.g. 22]

# .github/workflows/auto-response.yml
name: Auto Response

on:
  issues:
    types: [opened]

jobs:
  auto-respond:
    runs-on: ubuntu-latest
    steps:
      - name: Add welcome comment
        uses: actions/github-script@v6
        with:
          script: |
            await github.rest.issues.createComment({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.issue.number,
              body: `Thanks for opening this issue! Our team will review it shortly.
              Please check our [contributing guidelines](CONTRIBUTING.md) for more information.`
            });

## New Issue Triage

- [ ] Issue has clear, descriptive title
- [ ] Issue has sufficient details
- [ ] Issue type identified (bug/enhancement/question)
- [ ] Appropriate labels applied
- [ ] Duplicate search performed
- [ ] Assignee or team identified
- [ ] Priority level set
- [ ] Milestone assigned (if applicable)
- [ ] Related issues linked
- [ ] Welcome comment added (if needed)

## Weekly Triage Checklist

- [ ] Review all `status: needs-triage` issues
- [ ] Update stale issues
- [ ] Close resolved issues
- [ ] Re-prioritize based on team capacity
- [ ] Review and update milestones
- [ ] Identify and block spam
- [ ] Review unassigned issues
- [ ] Update project board

# List issues needing triage
gh issue list --label "status: needs-triage"

# Add labels to issue
gh issue edit 123 --add-label "priority: high,component: api"

# Assign issue
gh issue edit 123 --assignee @username

# Close issue
gh issue close 123 --comment "Fixed in version 2.0.0"

# Reopen issue
gh issue reopen 123

# Create issue from template
gh issue create --template bug_report.md

# Search for duplicates
gh issue search "error message in:title"

# View issue details
gh issue view 123

# Transfer issue to another repo
gh issue transfer 123 new-owner/new-repo

opened → needs-triage → in-progress → done
opened → needs-info → in-progress → done
opened → wontfix → closed
opened → duplicate → closed
opened → blocked → in-progress → done