Skip to content

feat: gstack-pr-triage — classify and order community PRs for /autoplan#369

Open
HMAKT99 wants to merge 1 commit intogarrytan:mainfrom
HMAKT99:arun/pr-triage-tool
Open

feat: gstack-pr-triage — classify and order community PRs for /autoplan#369
HMAKT99 wants to merge 1 commit intogarrytan:mainfrom
HMAKT99:arun/pr-triage-tool

Conversation

@HMAKT99
Copy link
Contributor

@HMAKT99 HMAKT99 commented Mar 23, 2026

Summary

  • Fetches open community PRs, classifies (security/fix/test/docs/feature), suggests merge order
  • JSON output to stdout — pipe to /autoplan for automated merge planning
  • Detects file conflicts between PRs
$ gstack-pr-triage --category fix | jq '.prs[:3][] | {number, category, risk}'
{"number": 332, "category": "fix", "risk": "low"}
{"number": 269, "category": "fix", "risk": "high"}

1 file, 137 lines

bin/gstack-pr-triage

Test plan

  • All existing tests pass
  • Classifies 47 community PRs

…toplan

Fetches open community PRs, classifies them (security/fix/test/docs/feature),
assesses risk (core file changes, size, missing tests), detects file conflicts
between PRs, and suggests merge order (security first, features last).

Outputs structured JSON to stdout for /autoplan consumption.

Usage:
  gstack-pr-triage                  # all open community PRs
  gstack-pr-triage 154 155 156      # specific PRs
  gstack-pr-triage --category fix   # filter by type
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.

1 participant