Add agentic workflow issue-triage #19057
Conversation
.github/workflows/issue-triage.md
Outdated
| <!-- You can customize prompting and tools in .github/workflows/agentics/issue-triage.config --> | ||
| @include? agentics/issue-triage.config |
There was a problem hiding this comment.
We don't have this file, but I assume that @include? means only include when it's available?
.github/workflows/issue-triage.md
Outdated
| on: | ||
| issues: | ||
| types: [opened, reopened] | ||
| stop-after: +30d # workflow will no longer trigger after 30 days. Remove this and recompile to run indefinitely |
There was a problem hiding this comment.
Does this mean that it will not analyze issues that are at least 30days old?
There was a problem hiding this comment.
I think it means that the workflow will only run for a month after committing it: https://githubnext.github.io/gh-aw/reference/frontmatter/#stop-after-configuration-stop-after
Let's set to 1d just to make sure we don't screw up anything haha
|
auto-created the pr sorry! I want to tweak this more haha and actually test it |
philipp-spiess
force-pushed
the
add-workflow-workflows-issue-triage.md-3051
branch
from
453319e to
a694e02
Compare
philipp-spiess
force-pushed
the
add-workflow-workflows-issue-triage.md-3051
branch
from
a694e02 to
d3a0fe9
Compare
| - Fetch the list of labels available in this repository. Use 'gh label list' bash command to fetch the labels. This will give you the labels you can use for triaging issues. | ||
| - Retrieve the issue content using the `get_issue` | ||
| - Fetch any comments on the issue using the `get_issue_comments` tool | ||
| - Find similar issues if needed using the `search_issues` tool |
There was a problem hiding this comment.
This is the part I'm most excited about so far!
|
|
||
| 4. Verify that the GitHub issue is related to Tailwind CSS and appears to be a bug. Feature requests and ideas should be created in the discussions area. If the GitHub issue does not appear to be a Tailwind CSS bug, read the `CONTRIBUTING.md` file and write a helpful comment explaining how we track bugs here. | ||
|
|
||
| 5. Validate that the GitHub issue contains instructions of a reproduction. Inline instructions or URL to a reproduction are valid. If no reproduction is found, read the `CONTRIBUTING.md` file and write a helpful comment asking for one. Then, add the `needs reproduction` tag. |
Co-authored-by: Robin Malfait <[email protected]>
Yeah that's a good idea I'll do some deleting |
This PR attempts to set up an automatic issue triaging tool using Claude Code as the agent and GitHub Agentics as the framework: https://githubnext.github.io/gh-aw/start-here/quick-start/
Based on the
safe-outputssetting, this agent can only label issues or write replies. Let's see how useful that is 🤷You can't run it locally since it does not have a manual trigger and needs a new github issue instead so my plan is to merge it and then create some super legit issues to see if it works!
Test plan