Skip to content

Triage command followup fixes/tweaks#21629

Merged
jmchilton merged 3 commits intogalaxyproject:devfrom
dannon:issue-triage-followup
Jan 20, 2026
Merged

Triage command followup fixes/tweaks#21629
jmchilton merged 3 commits intogalaxyproject:devfrom
dannon:issue-triage-followup

Conversation

@dannon
Copy link
Copy Markdown
Member

@dannon dannon commented Jan 20, 2026

Follow-up to #21579 with a few fixes and improvements.

Fixes

  • File path references: triage-issue.md was pointing to bug-triage.md and feature-triage.md but the actual files are named triage-bug.md and triage-feature.md
  • gh CLI syntax: Both specialized commands had "gh view issue" instead of "gh issue view <number>"

Improvements

  • Output directory: Added explicit instruction that artifacts are written to the current working directory
  • Parallel execution: Clarified that independent subagent tasks can run in parallel since subagents communicate through artifact files, not shared context. Tasks that only need the original issue (e.g., code research + importance assessment) can run concurrently, while tasks that depend on earlier artifacts (e.g., planning needs code research) must wait.

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

The command was pointing to bug-triage.md and feature-triage.md but the
actual files are named triage-bug.md and triage-feature.md.
Changed "gh view issue" to "gh issue view <number>" to match the correct
gh CLI syntax.
Two related improvements to the triage commands:

1. Explicitly state that artifacts are written to the current working
   directory, so users know where to find the output files.

2. Clarify parallel vs serial subagent execution. Subagents don't share
   context - they communicate through the artifact files they create.
   Tasks that only need the original issue can run in parallel (e.g.,
   code research + importance assessment), while tasks that need to read
   earlier artifacts must wait (e.g., planning depends on code research).
@dannon dannon marked this pull request as ready for review January 20, 2026 17:06
@github-actions github-actions Bot added this to the 26.1 milestone Jan 20, 2026
@jmchilton jmchilton merged commit db9565a into galaxyproject:dev Jan 20, 2026
52 checks passed
@jmchilton
Copy link
Copy Markdown
Member

Yeah - I even hit one of those. Thanks for the fixes - really nice!

@github-actions
Copy link
Copy Markdown

This PR was merged without a "kind/" label, please correct.

@itisAliRH itisAliRH deleted the issue-triage-followup branch March 9, 2026 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants