Restore Pages deployment after optional CI skips #108
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kaiba/kaiba-provisioning!108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/pages-deployment-gate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Main CI could pass while its Pages deployment was skipped: the aggregate depends on an intentionally skipped optional ARM backend, and Pages inherited GitHub’s implicit
success()condition through that dependency chain. This happened in main run 37152567895.Use an explicit
!cancelled()condition and require successful direct dependencies. Deployment stays limited to main push/manual runs and remains blocked when required checks fail or the run is cancelled, following GitHub’s status-function rules.Validation: pinned actionlint workflow/expression checks;
nix fmt -- --ci(zero changes); independent gate review; passing PR CI, main CI, and final input isolation. Maine4a99d494fa69080fe437800af91c4fb00ca8971deployed Pages successfully; deployment 6833358042 independently reports that exact commit and a successful status. Both Hydra routing flags remain disabled.