Skip to content

Fix agent skipping assign-to-agent call in security-alert-burndown workflow #12358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mnkiefer merged 4 commits into from
Jan 28, 2026
+46 −30
Merged

Fix agent skipping assign-to-agent call in security-alert-burndown workflow #12358

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7b116e3
Initial plan
Copilot Jan 28, 2026
059628e
Improve security-alert-burndown workflow instructions for assign-to-a…
Copilot Jan 28, 2026
000dd74
Merge branch 'main' into copilot/fix-assign-to-agent-step
mnkiefer Jan 28, 2026
2f24e06
Final validation: workflow compiles successfully
Copilot Jan 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 24 additions & 16 deletions .github/workflows/security-alert-burndown.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

36 changes: 22 additions & 14 deletions .github/workflows/security-alert-burndown.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,9 +82,13 @@ For each discovered item (up to 100 total per run):
- `start_date`: Item created date (YYYY-MM-DD format)
- `end_date`: Item closed date (YYYY-MM-DD format) or today's date if still open

### Step 4: Assign work
### Step 4: Create parent issue and assign work

After updating project items, **create one parent tracking issue** that captures the bundling plan and links the PRs, then **assign that issue to an agent**.
After updating project items, you must complete **all three actions below in order**:

1. **Create the parent tracking issue**
2. **Add the issue to the project board**
3. **Assign the issue to the Copilot agent**

**Selection Criteria:**
1. Review all discovered PRs
Expand All @@ -106,7 +110,7 @@ After updating project items, **create one parent tracking issue** that captures
- Enforce **one runtime + one target file per PR**.
- All PRs must pass **CI and relevant runtime tests** before merge.

**Create Parent Issue:**
**Action 1: Create the parent issue**

Create a single issue that contains:
- The bundling rules (copied below)
Expand All @@ -119,9 +123,11 @@ Use the `create_issue` tool:
create_issue(title="Security Alert Burndown: Dependabot bundling plan (YYYY-MM-DD)", body="<paste body from template below>")
```

**Add Parent Issue to the Campaign Board:**
After calling `create_issue`, **store the returned issue number** - you will need it for actions 2 and 3.

**Action 2: Add the issue to the project board**

Immediately after creating the issue, add it to the project board using `update_project` (so it’s tracked like the other campaign items):
Immediately after creating the issue, add it to the project board using `update_project`. Use the issue number from action 1:

```
update_project(
Expand All @@ -140,8 +146,18 @@ update_project(
)
```

**Issue Body Template (paste into `body=`):**
**Action 3: Assign the issue to the agent**

Finally, assign the issue to the Copilot agent using `assign_to_agent`. Use the issue number from action 1:

```
assign_to_agent(issue_number=<new_issue_number>, name="copilot")
```

**CRITICAL**: You must call all three tools (create_issue, update_project, assign_to_agent) in sequence to complete this step. Do not skip any of them.


**Issue Body Template:**
```markdown
## Context
This issue tracks Dependabot PR bundling work discovered by the Security Alert Burndown campaign.
Expand Down Expand Up @@ -171,14 +187,6 @@ PRs:
5. Update this issue checklist as PRs are merged.
```

**Assign Parent Issue to Agent:**

After creating the issue, call `assign_to_agent` and explicitly provide the `issue_number` of the new issue (since `target: "*"`):

```
assign_to_agent(issue_number=<new_issue_number>, name="copilot")
```

### Step 5: Report

Summarize how many items were discovered and added/updated on the project board, broken down by category, and include the parent tracking issue number that was created and assigned.
Expand Down
Loading