Skip to content

Add gh-aw issue triage workflow#5635

Open
theletterf wants to merge 2 commits intomainfrom
fabri/gh-aw-issue-triage
Open

Add gh-aw issue triage workflow#5635
theletterf wants to merge 2 commits intomainfrom
fabri/gh-aw-issue-triage

Conversation

@theletterf
Copy link
Copy Markdown
Member

@theletterf theletterf commented Mar 26, 2026

Summary

  • Adds a GitHub Agentic Workflow (gh-aw) that automates issue triage in docs-content
  • Triggered by typing /triage on an issue comment (only users with write access) or via manual workflow_dispatch for batch processing
  • Analyzes issue content (title, body, URLs, labels) and applies the correct Team:* label
  • Uses the Elastic Docs MCP server to look up referenced documentation pages
  • Derives team ownership from CODEOWNERS; can fetch CODEOWNERS from other repos for cross-repo issues
  • Labels an issue can receive: Team:Admin, Team:Developer, Team:DocsEng, Team:Experience, Team:Ingest, Team:Projects, cross-team
  • Once a team label is applied, the existing add-to-board.yml workflow handles board routing

How it works

  1. Someone comments /triage on an issue (or dispatches manually for batch mode)
  2. Pre-steps fetch the issue data and CODEOWNERS to JSON
  3. The AI agent reads the issue, uses the Elastic Docs MCP server to gather context about referenced pages
  4. For docs stored outside docs-content, it fetches the relevant repo's CODEOWNERS via gh api
  5. It applies the best-fit team label via safe-output (add-labels)

🤖 Generated with Claude Code

Add a GitHub Agentic Workflow that triages docs-content issues by
analyzing their content and applying the correct team label. The
workflow is triggered by typing `/triage` on an issue comment (write
access required) or via manual workflow_dispatch for batch processing.

Features:
- Uses Elastic Docs MCP server to look up referenced pages
- Derives team ownership from CODEOWNERS
- Can fetch CODEOWNERS from other repos for cross-repo issues
- Supports batch triage of all open needs-team issues

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@theletterf theletterf requested review from a team as code owners March 26, 2026 09:59
@theletterf theletterf requested a review from cotti March 26, 2026 09:59
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 26, 2026

🔍 Preview links for changed docs

Copy link
Copy Markdown
Member

@florent-leborgne florent-leborgne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits on the paths for my team and the dev-docs team

Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
@theletterf
Copy link
Copy Markdown
Member Author

@shainaraskas @szabosteve Could you review as well? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants