Repository navigation
feat(lastcode): make GitHub CI merge authority - #111
Merged
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #103
Ordinary LastCode PRs still required a local Full CI stamp even after GitHub CI and resumable waiting became authoritative. This cutover makes the guarded merge re-read the same exact GitHub workflow evidence as Wait for PR, refetch and confirm the base, and require a clean current PR before the exact-head squash merge.
It removes the ordinary Run Full CI Project Action and updates the LastCode delivery workflows. Checkpoint and release Full CI stamps remain unchanged.
Validation:
Authored by GPT-5.6-sol via the Codex harness.