feat: Add GitHub issue automation with issue metadata #350

JackYPCOnline · 2025-12-12T03:41:28Z

Add GitHub Actions workflow for automated issue processing
Implement project field management for GitHub Projects v2
Add task labeller action for issue categorization
Enhance GitHub tools with optimized project operations
Add automation configuration for issue metadata

Description

This RP helps add issue metadata, help identify and summerize the issue, then tag the area of expert in the comments.

Tested in my fork.

Related Issues

Hack day feature.

Documentation PR

Type of Change

Bug fix
New feature
Breaking change
Documentation update
Other (please describe):

Testing

How have you tested the change?

[x ] I ran npm run check

Checklist

[x ] I have read the CONTRIBUTING document
[x ] I have added any necessary tests that prove my fix is effective or my feature works
[x ] I have updated the documentation accordingly
[x ] I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
[x ] My changes generate no new warnings
[x ] Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

- Add GitHub Actions workflow for automated issue processing - Implement project field management for GitHub Projects v2 - Add task labeller action for issue categorization - Enhance GitHub tools with optimized project operations - Add automation configuration for issue metadata

- Remove automatic Status field setting to Todo - Only update the specifically requested project field - Remove debug logging and incomplete functions

- Update system prompt to tag only the 2 most related experts - Prioritize experts most closely related to specific issue content - Reduce notification noise while maintaining relevant expertise

.github/config/automation-config.json

.github/actions/strands-task-labeller/action.yml

.github/scripts/python/github_tools.py

zastrowm · 2025-12-17T18:22:26Z

.github/actions/strands-task-labeller/action.yml

Can we have some examples of this working? I'd like to evaluate it before adding this

Action: https://github.com/JackYPCOnline/sdk-typescript/actions/runs/20180281490/job/57938749701
Issue: JackYPCOnline#12
Are you able to access the links?

zastrowm · 2025-12-17T18:26:17Z

.github/config/automation-config.json

+      "name": "Gemini Model Provider",
+      "github_usernames": ["notgitika"]
+    },
+    "litellm": {


Would it be better to list the the label associated with the category? Or are we allowing any label?

Right now all of our "area" label start with "area-"

For labels, the agent will only use existing labels. It will @ the person in this list in the comment, thus the expert will receive an email noticification. We can do assign the expert directly, but personally I think this is a little aggressive.

Agreed, we shouldn't assign. I like mentioning more.

But we do have to be concerned with user-submitted content possibly spamming the repository via the agent. Some sort of guard rails around what the agent can do I think would be ideal.

zastrowm · 2025-12-17T18:26:47Z

.github/scripts/python/github_tools.py

+    Returns:
+        Result of the operation
+    """
+    result = _github_request("POST", f"issues/{issue_number}/labels", repo, {"labels": labels})


Similar question to above, I wonder if we should be validating that the label is allow-listed to the subset of "known" labels.

Alternatively, we should validate/require that the label already exists

This agent pull existing labels only and apply them, it can create labels if we adjust system prompt.

This agent pull existing labels only and apply them

Can you trick it into applying 200 new labels? And on unrelated issues?

zastrowm · 2025-12-17T18:29:42Z

.github/workflows/issue-metadata-automation.yml

+    types: [opened,reopened]
+permissions:
+  contents: write
+  issues: write


We should be architecting this similar to the existing agents. Right now, we have two stages:

Agent runs in a readonly sandbox

A sub-subsequent job/stage takes the output of (1) and updates writable things as appropriate. This is to help avoid the agent from having too many permissions, like updating unrelated PRs & Issues. I think we should be doing the same thing here.

zastrowm · 2025-12-17T18:30:44Z

.github/workflows/issue-metadata-automation.yml

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


We don't currently have any workflows that run agents automatically and on arbitrary issues. We'll have to evaluate how we do this. Right now all agents are "opt-in" while this is "automatic on all" which has some security concerns I think

That is an interesting topic we need to think about since we want an agent to be automated.

JackYPCOnline temporarily deployed to auto-approve December 12, 2025 03:41 — with GitHub Actions Inactive

fix: prevent automatic status field changes in project operations

928560b

- Remove automatic Status field setting to Todo - Only update the specifically requested project field - Remove debug logging and incomplete functions

JackYPCOnline had a problem deploying to auto-approve December 12, 2025 03:51 — with GitHub Actions Failure

feat: limit expert tagging to 2 most relevant people

1754f15

- Update system prompt to tag only the 2 most related experts - Prioritize experts most closely related to specific issue content - Reduce notification noise while maintaining relevant expertise

JackYPCOnline had a problem deploying to auto-approve December 12, 2025 04:01 — with GitHub Actions Failure

fix:restrict inline policy

79309ff

JackYPCOnline had a problem deploying to auto-approve December 12, 2025 04:06 — with GitHub Actions Failure

JackYPCOnline changed the title ~~feat: add GitHub issue automation with project fields and labeling~~ feat: Add GitHub issue automation with issue metadata Dec 12, 2025

JackYPCOnline marked this pull request as ready for review December 12, 2025 15:29

dbschmigelski reviewed Dec 12, 2025

View reviewed changes

.github/config/automation-config.json Outdated Show resolved Hide resolved

.github/config/automation-config.json Outdated Show resolved Hide resolved

.github/config/automation-config.json Outdated Show resolved Hide resolved

JackYPCOnline had a problem deploying to auto-approve December 12, 2025 21:03 — with GitHub Actions Failure

JackYPCOnline temporarily deployed to auto-approve December 12, 2025 21:18 — with GitHub Actions Inactive

JackYPCOnline had a problem deploying to auto-approve December 12, 2025 21:27 — with GitHub Actions Failure

JackYPCOnline added 4 commits December 12, 2025 16:41

refactor: remove prioritization and make labels dynamic

200a3fb

feat: enhance issue triage with similar issue search

751d378

fix: enforce using only existing repository labels

9ac377c

Update automation-config.json

7a6ba30

JackYPCOnline force-pushed the github-automation-enhancements branch from 39cd167 to 7a6ba30 Compare December 12, 2025 21:52

JackYPCOnline temporarily deployed to auto-approve December 12, 2025 21:52 — with GitHub Actions Inactive

JackYPCOnline requested a review from dbschmigelski December 12, 2025 21:52

afarntrog reviewed Dec 16, 2025

View reviewed changes

.github/actions/strands-task-labeller/action.yml Show resolved Hide resolved

.github/scripts/python/github_tools.py Show resolved Hide resolved

JackYPCOnline requested a review from afarntrog December 17, 2025 15:05

zastrowm requested changes Dec 17, 2025

View reviewed changes

feat: Add GitHub issue automation with issue metadata #350

Are you sure you want to change the base?

feat: Add GitHub issue automation with issue metadata #350

Uh oh!

Conversation

JackYPCOnline commented Dec 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Related Issues

Documentation PR

Type of Change

Testing

Checklist

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JackYPCOnline Dec 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

JackYPCOnline commented Dec 12, 2025 •

edited

Loading

JackYPCOnline Dec 17, 2025 •

edited

Loading