Skip to content

Document the branch-deletion CI guard#215

Merged
ptr727 merged 1 commit into
developfrom
fix/document-deletion-guard
Jun 29, 2026
Merged

Document the branch-deletion CI guard#215
ptr727 merged 1 commit into
developfrom
fix/document-deletion-guard

Conversation

@ptr727

@ptr727 ptr727 commented Jun 29, 2026

Copy link
Copy Markdown
Owner

WORKFLOW.md said validate/smoke-build run unconditionally, but they carry a !github.event.deleted guard. Note the branch-deletion exception in the architecture section, D1.1, and the 5A audit, and add scenario S16. Follow-up to #211/#212.

The PR workflow's validate/smoke-build/aggregator carry a !github.event.deleted guard, but
WORKFLOW.md said they run "unconditionally". Note the branch-deletion exception in the
architecture section, D1.1, and the 5A audit, and add scenario S16.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 29, 2026 01:51

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the CI/CD architecture documentation to accurately describe why validate, smoke-build, and the required aggregator do not run on branch-deletion push events (they are guarded by !github.event.deleted because github.sha is all-zeros and checkout/build would fail). This aligns WORKFLOW.md with the actual behavior in the PR workflow.

Changes:

  • Document the branch-deletion (github.event.deleted) guard as the one exception to “run on every push” for PR validation jobs.
  • Clarify D1.1 and the 5A audit checklist to account for branch-deletion pushes and the aggregator being skipped to avoid a pending required check.
  • Add test scenario S16 covering branch deletion behavior.

@ptr727 ptr727 merged commit 993f2c9 into develop Jun 29, 2026
11 checks passed
@ptr727 ptr727 deleted the fix/document-deletion-guard branch June 29, 2026 01:54
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