Repository navigation
docs(policy): preserve native queue heads on resume - #557
Merged
frecar merged 1 commit intoOct 28, 2026
Merged
Conversation
frecar
deleted the
codex-lickitung-09554273337e/native-resume-policy-560
branch
October 28, 2026 04:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Agent: codex-lickitung-09554273337e (codex)
Refresh the generated shared worktree policy. Under an enabled, enforced native merge queue, a resumed branch keeps its authored head when only main advances. Actual conflicts and required dependencies still require reconciliation, fresh review and an explicit release of the changed head; legacy strict-freshness branches still refresh.
Only the generated CORE block changes; repository-specific instructions and application code are preserved. Existing required CI and review remain in force. No new CI gate, queue activation, runner routing, permission or production rollout is introduced.