Skip to content

Remove schedule triggers from security alert burndown campaign workflows#11993

Merged
mnkiefer merged 3 commits intomainfrom
copilot/remove-schedule-triggers
Jan 27, 2026
Merged

Remove schedule triggers from security alert burndown campaign workflows#11993
mnkiefer merged 3 commits intomainfrom
copilot/remove-schedule-triggers

Conversation

Copy link
Contributor

Copilot AI commented Jan 27, 2026

Converted four security alert burndown workflows from scheduled to manual-only execution by removing their schedule: triggers.

Changes

  • code-scanning-fixer.md: Removed schedule: every 30m
  • dependabot-bundler.md: Removed schedule: every 6h
  • secret-scanning-triage.md: Removed schedule: every 6h
  • security-fix-pr.md: Removed schedule: every 4h

All workflows retain workflow_dispatch for manual triggering. Lock files regenerated accordingly.

Original prompt

Remove schedule: triggers from the following, as they are part of the security alert burndown campaign:
code-scanning-fixer.md
dependabot-bundler.md
secret-scanning-triage.md
security-fix-pr.md


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

Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot AI changed the title [WIP] Remove schedule triggers from security alert burndown campaign Remove schedule triggers from security alert burndown campaign workflows Jan 27, 2026
Copilot AI requested a review from mnkiefer January 27, 2026 05:03
@mnkiefer mnkiefer marked this pull request as ready for review January 27, 2026 05:12
@mnkiefer mnkiefer merged commit fa61b63 into main Jan 27, 2026
50 checks passed
@mnkiefer mnkiefer deleted the copilot/remove-schedule-triggers branch January 27, 2026 05:34
Mossaka added a commit that referenced this pull request Jan 27, 2026
#11969)

* Initial plan

* Investigate firewall 0 requests issue

Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>

* Fix AWF command quoting to ensure agent runs inside firewall container

The compound command after -- was not properly quoted, causing the &&
operator to be interpreted by the outer shell. This resulted in:
1. AWF container running only the PATH export (which exits immediately)
2. Copilot agent running on the host AFTER the firewall container stopped
3. Firewall reporting 0 requests

Now the entire command is wrapped in single quotes so it's passed to AWF
as a single argument, ensuring Copilot runs inside the firewall container.

Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>

* Add changeset [skip-ci]

* 🔧 Improve interactive workflow add experience (#11966)

* interactive add

* interactive add

* fix lint

* review

* fix quick start

* fix quick start

* fix line break

* Add upgrade, import, and debug sections to agentic authoring docs (#11987)

* various minor tweaks to ux (#11988)

* Fix release workflow: Clarify MCP tool call vs bash file operations (#11991)

* chore: rm schedule triggers from security alert burndown campaign workers (#11993)

* Merge main and regenerate workflows

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Add changeset [skip-ci]

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Co-authored-by: Jiaxiao Zhou <duibao55328@gmail.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Don Syme <dsyme@users.noreply.github.com>
Co-authored-by: Don Syme <dsyme@github.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
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