Skip to content

Latest commit

 

History

History
65 lines (41 loc) · 2.38 KB

File metadata and controls

65 lines (41 loc) · 2.38 KB

🏷️ Issue Triage

For an overview of all available workflows, see the main README.

The issue triage workflow will when issues are created or reopened to triage issues in the repository.

Installation

# Install the 'gh aw' extension
gh extension install github/gh-aw

# Add the Issue Triage workflow to your repository
gh aw add githubnext/agentics/issue-triage

This walks you through adding the workflow to your repository.

You must also choose a coding agent and add an API key secret for the agent to your repository.

You can't start a run of this workflow directly as it is triggered in the context of an issue.

Mandatory Checklist

  • If in a fork, enable GitHub Actions and Issues in the fork settings

Configuration

This workflow requires no configuration and works out of the box. You can use local configuration to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in .github/workflows/agentics/issue-triage.config.md.

  1. Add MCPs to integrate with project management tools

After editing run gh aw compile to update the workflow and commit all changes to the default branch.

What it reads from GitHub

  • The specific issue being triaged and its details
  • Repository contents and file structure
  • Pull requests and their metadata
  • Actions workflow runs and results
  • Checks and status information

What it creates

  • Adds comments to issues with triage information
  • Updates issue labels, assignees, or other metadata
  • Requires issues: write permission

What web searches it performs

  • Searches for relevant information to assist with issue triage
  • May look up documentation, error messages, or similar issues

Human in the loop

  • Review triage comments added to issues for accuracy
  • Validate label assignments and priority assessments
  • Override or adjust triage decisions when needed
  • Monitor triaged issues to ensure proper follow-up and resolution
  • Disable or uninstall the workflow if triage automation is not accurate or helpful

Activity duration

  • By default this workflow will trigger for at most 30 days, after which it will stop triggering.
  • This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.