Repository navigation
feat(lastcode): prove hosted CI waiting - #104
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The existing waiter assumes that every PR must eventually report a hosted check, so repositories with CI disabled can wait forever. Before GitHub CI can become authoritative, we also need one stable aggregate gate tied to the exact synthesized PR merge revision.
This change moves the existing workflow onto standard GitHub runners, adds a fail-closed
CI Gate, and teachesWait for PRto distinguish disabled/non-required CI from an enabled workflow that has not registered yet. The waiter binds local branch, worktree, PR, head, base, merge revision, workflow run, and aggregate job identity; it wakes on actionable failures or bounded missing-registration states while keeping clean review completion asleep until all passive gates are ready.Focused validation: 41 tests across the workflow policy, GitHub-CI evaluator, and waiter; scripts-package typecheck; focused lint; YAML parse; diff check. The branch was published with
--no-verifyto avoid the known blocking Quick CI hook; the existing Full CI stamp remains required for guarded merge during this proof slice.Part of #103.
Implemented with GPT-5.6 Sol in the Codex harness.