Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 28, 2026

Problem

In run 21454338976, the agent created parent issue #12356 but never called assign_to_agent. The conditional step contains(needs.agent.outputs.output_types, 'assign_to_agent') skipped because the agent didn't emit that output type.

Root cause: Workflow instructions had three required actions scattered across 100 lines with a 50-line issue template interrupting the sequence:

  • Action 1: Create issue (lines 109-124)
  • Action 2: Add to project (lines 126-147)
  • Issue template (lines 149-188)
  • Action 3: Assign to agent (lines 190-197)

Changes

Restructured Step 4 to make the three-action sequence explicit and uninterruptible:

  • Sequential numbering: Changed header to "Step 4: Create parent issue and assign work" with numbered list: "1. Create the parent tracking issue, 2. Add the issue to the project board, 3. Assign the issue to the Copilot agent"
  • Action labels: Renamed subsections from descriptive headers to "Action 1", "Action 2", "Action 3"
  • Issue number reminder: Added note after Action 1 to store the returned issue number for use in Actions 2 and 3
  • Critical warning: Added **CRITICAL**: You must call all three tools (create_issue, update_project, assign_to_agent) in sequence
  • Template relocation: Moved 50-line issue body template after all actions to prevent interrupting the sequence

The workflow structure remains unchanged—only the embedded prompt text was updated. The conditional logic contains(needs.agent.outputs.output_types, 'assign_to_agent') is correct; the issue was agent behavior, not the conditional.

File changes

  • .github/workflows/security-alert-burndown.md - Restructured Step 4 instructions (+8 lines, -14 lines)
  • .github/workflows/security-alert-burndown.lock.yml - Recompiled with updated embedded prompt
Original prompt

Analyze this run: https://github.com/githubnext/gh-aw/actions/runs/21454338976/job/61791632772
The parent issue was created, but the assign-to-agent step was skipped when it should have assigned the agent.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

…gent

- Restructure Step 4 with clear numbered actions (1, 2, 3)
- Add explicit reminder to store issue number after create_issue
- Add CRITICAL note that all three tools must be called
- Move issue template after all action instructions
- Make instructions more sequential and actionable

This should prevent the agent from skipping the assign_to_agent call.

Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
@mnkiefer mnkiefer marked this pull request as ready for review January 28, 2026 20:51
mnkiefer and others added 2 commits January 28, 2026 21:51
@mnkiefer
Copy link
Contributor

@copilot recompile workflow

Copilot AI changed the title [WIP] Fix assign to agent step in run analysis Fix agent skipping assign-to-agent call in security-alert-burndown workflow Jan 28, 2026
Copilot AI requested a review from mnkiefer January 28, 2026 20:54
Copy link
Contributor Author

Copilot AI commented Jan 28, 2026

@copilot recompile workflow

Workflow recompiled successfully. No changes were needed - the lock file was already up to date with the markdown changes.

@mnkiefer mnkiefer merged commit 4c899ff into main Jan 28, 2026
125 checks passed
@mnkiefer mnkiefer deleted the copilot/fix-assign-to-agent-step branch January 28, 2026 21:01
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.

2 participants