Fix missing staged environment variable in create-discussion jobs

[Copilot]

This PR addresses the requirement to review all test agentic workflows in the repository and ensure that workflows marked with staged: true have the GITHUB_AW_SAFE_OUTPUTS_STAGED environment variable properly code generated in their lock files.

Analysis Results

After comprehensive investigation, a missing staged environment variable was found and fixed in create-discussion jobs.

Issue Identified:

While most safe output types correctly included the staged environment variable, create-discussion jobs were missing the GITHUB_AW_SAFE_OUTPUTS_STAGED environment variable in their job configuration.

Changes Made:

1. Fixed Compiler Logic: Added missing staged environment variable logic to buildCreateOutputDiscussionJob function in pkg/workflow/compiler.go
2. Consistent Pattern: Create-discussion jobs now match the pattern used by create-issue and create-pull-request jobs
3. Recompiled Workflow: Updated test-safe-output-create-discussion.lock.yml to include the staged variable

Verification Results:

Before Fix:

• Custom engine steps had GITHUB_AW_SAFE_OUTPUTS_STAGED: "true" ✅
• Create-discussion job was missing the environment variable ❌

After Fix:

• Custom engine steps: GITHUB_AW_SAFE_OUTPUTS_STAGED: "true" ✅
• Create-discussion job: GITHUB_AW_SAFE_OUTPUTS_STAGED: "true" ✅
• JavaScript code properly checks this environment variable ✅

Validated Workflows:

• test-safe-output-add-issue-comment.md ✅
• test-safe-output-add-issue-label.md ✅
• test-safe-output-create-code-scanning-alert.md ✅
• test-safe-output-create-discussion.md ✅ (now fixed)
• test-safe-output-create-issue.md ✅
• test-safe-output-create-pull-request-review-comment.md ✅
• test-safe-output-create-pull-request.md ✅
• test-safe-output-missing-tool.md ✅
• test-safe-output-push-to-pr-branch.md ✅
• test-safe-output-update-issue.md ✅

The staging functionality now works correctly across all safe output types - workflows with staged: true in their frontmatter properly generate the environment variable in both custom engine steps and safe output processing jobs.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[pelikhan]

@copilot double check create-discussion and make sure the staged environment variable is set on that step

[Copilot]

@copilot double check create-discussion and make sure the staged environment variable is set on that step

I've verified the create-discussion step and found that it was missing the staged environment variable. The issue has been fixed in commit ca0c328.

What was wrong:

• Create-discussion jobs were missing the GITHUB_AW_SAFE_OUTPUTS_STAGED: "true" environment variable
• While custom engine steps had it correctly set, the create-discussion job itself didn't receive it

What was fixed:

• Added the staged environment variable logic to buildCreateOutputDiscussionJob in the compiler
• Now matches the pattern used by create-issue and create-pull-request jobs
• Recompiled the test workflow to include the staged variable

Verification:
The create-discussion workflow now correctly has the staged environment variable set at line 1128 of the lock file, allowing the JavaScript code to properly detect staged mode and show a preview instead of creating actual discussions.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.contoso.com
  • Triggering command: /tmp/go-build1755024240/b278/cli.test -test.testlogfile=/tmp/go-build1755024240/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)
  • Triggering command: /tmp/go-build3567036355/b278/cli.test -test.testlogfile=/tmp/go-build3567036355/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)