Add issue triage workflow (thin trigger for docs-actions)#5635
Merged
Conversation
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>
Contributor
🔍 Preview links for changed docs |
florent-leborgne
approved these changes
Mar 30, 2026
florent-leborgne
left a comment
florent-leborgne
left a comment
Member
There was a problem hiding this comment.
LGTM, some nits on the paths for my team and the dev-docs team
Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
Member
Author
|
@shainaraskas @szabosteve Could you review as well? Thanks! |
4 tasks
Replace standalone gh-aw workflow (source .md + compiled .lock.yml) with a thin trigger that calls the centralized issue-triage workflow from elastic/docs-actions. Team mapping is passed via additional-instructions. Depends on elastic/docs-actions#57 being merged and released. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
theletterf
changed the title
shainaraskas
approved these changes
Apr 2, 2026
shainaraskas
left a comment
shainaraskas
left a comment
Member
There was a problem hiding this comment.
nice! likely good enough for 90% (sorry reviewing this took me so long)
couple comments on keywords + also the fallback behavior
Member
|
for longevity, could this be made to reference the ownership mappings in codeowners? |
Address feedback from florent-leborgne and shainaraskas: - Fix Team:Experience paths (reference/kibana/, reference/observability/) - Fix Team:Developer paths (reference/machine-learning/, cross-project-search) - Replace broad "security" in Team:Admin with specific terms - Add "subscriptions" to Team:Admin, bare "security" to Team:Experience - Change fallback from Team:Projects to cross-team Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
issue-triageagentic workflow from elastic/docs-actions/triageon an issue comment (write access required) or via manualworkflow_dispatchfor batch processingTeam:*labeladditional-instructions— the core triage logic lives in docs-actionsHow it works
/triageon an issue (or dispatches manually for batch mode)gh apiadd-labels)Dependencies
v1tag includes the lock file)COPILOT_GITHUB_TOKENsecret configured in this repoLabels an issue can receive
Team:Admin,Team:Developer,Team:DocsEng,Team:Experience,Team:Ingest,Team:Projects,cross-team🤖 Generated with Claude Code