Skip to content

refactor: temporary ID handling #12483

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 1 commit into from
Jan 29, 2026
Merged

refactor: temporary ID handling #12483

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
117 changes: 18 additions & 99 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.

31 changes: 7 additions & 24 deletions .github/workflows/security-alert-burndown.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,7 @@ safe-outputs:
max: 100
create-issue:
max: 1
assign-to-agent:
max: 1
name: copilot
allowed: [copilot]
target: "*"
assignees: [copilot]
project: https://github.com/orgs/githubnext/projects/144
---

Expand Down Expand Up @@ -84,19 +80,20 @@ For each discovered item (up to 100 total per run):

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

After updating project items, **first complete the bundling analysis below, then immediately perform all three safe-output calls in sequence**. Do not proceed to Step 5 until all three calls are complete.
After updating project items, **first complete the bundling analysis below, then immediately perform the safe-output calls below in sequence**. Do not proceed to Step 5 until the calls are complete.

#### Bundling Analysis (Do This First)

Before creating the issue, analyze the discovered PRs and determine which PRs to bundle together.

#### Required Safe-Output Calls (All Three Required):
#### Required Safe-Output Calls:

After completing the bundling analysis, you must immediately perform these three safe-output calls in order:
After completing the bundling analysis, you must immediately perform these safe-output calls in order:

1. **Call `create_issue`** to create the parent tracking issue
2. **Call `update_project`** to add the created issue to the project board
3. **Call `assign_to_agent`** to assign the created issue to Copilot

The created issue will be assigned to Copilot automatically via `safe-outputs.create-issue.assignees`.

#### Bundling Guidelines

Expand Down Expand Up @@ -155,22 +152,8 @@ update_project(
)
```

#### Safe-Output Call #3: Assign to Agent

**Immediately** call `assign_to_agent` using the temporary ID from call #1:

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

**Example**: If `create_issue` returned `aw_sec2026012901`, then:
**Example**: If `create_issue` returned `aw_sec2026012901`, then call:
- Call #2: `update_project(..., content_number="aw_sec2026012901", ...)`
- Call #3: `assign_to_agent(issue_number="aw_sec2026012901", name="copilot")`

The temporary ID will be automatically resolved to the real issue number during safe-output processing.


**Issue Body Template:**
Expand Down
Loading