INFRA-136: fail ci/ci aggregator on skipped needed jobs #74
No reviewers
Labels
No labels
app
bug
ci
compliance
dependencies
docs
documentation
duplicate
enhancement
good first issue
help wanted
infra
invalid
javascript
python
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: adam/exec-aide#74
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "INFRA-136-ci-standardization"
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?
Summary
CI standardization hygiene (INFRA-136, agent 12a). The inline
ci / ciaggregator green-lit the org-required status check when a needed job was SKIPPED:skippedis neitherfailurenorcancelled, so a conditionally-skipped required job could pass the org-required check without ever running.Fix
Treat
skippedas a failure in the aggregator condition (one-line change plus a comment). Pure hardening —pythonandtypescripthave noif:and cannot skip under current config, so this does not affect current green builds; it closes the latent hole.Deferred
The audit's prescribed remedy (Stub 4: a shared
callable-ci-aggregate.yamlreusable, converting exec-aide and proposal-system) is not applied here: it requires authoring a new org-wide reusable workflow in the.githubrepo with a cross-repo@maindependency, and is coupled to proposal-system (a closed topic, out of scope). Recommend a dedicated follow-up ticket to build the shared callable once and convert callers. This contained inline fix closes the actual bug for exec-aide in the meantime.Refs INFRA-136.
✅ Open SWE Review: No issues found
Open SWE reviewed this PR and found no potential bugs to report.
Open in Web