Repository navigation
Configure protected squash auto-merge - #4
Merged
Merged
Conversation
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
kixelated
marked this pull request as ready for review
November 7, 2026 17:11
kixelated
enabled auto-merge (squash)
November 7, 2026 17:11
This was referenced Nov 7, 2026
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.
Document squash auto-merge protected by required Check and up-to-date main. Rerun Check on PR edits so retargeted PRs receive feedback for their new base. The maintainer authorized this repository setup and continued quest-complete/quest-spawn.
GitHub native merge queues are limited to organization-owned repositories; this repository is personal. Use the supported latest-base validation instead of adding an unusable merge-group workflow.
Repository configuration
Auto-merge and merged-branch cleanup are enabled; squash is the only allowed merge method. Main's active ruleset blocks deletion and non-fast-forward updates, requires GitHub Actions Check, and requires the PR branch to be current with main. The administrator escape matches moq's ruleset; the workflow never bypasses protection. The plan PR landed through the normal merge command after its checks and independent review passed. No direct merge was used.
Validation
nix develop --command quest gate just checkpasses: rustfmt, clippy, scaffold tests (none yet), and quest validation on 14 documents.git diff --checkpasses.Public API and wire impact
None. CI event handling and landing instructions only.
Caused by
New requested repository configuration; no earlier PR caused a bug.
Models
Size: M
Implementer: Codex, gpt-6.1-sol, xhigh effort
Review
Round 1: Claude Code, claude-opus-5-5, medium effort, 8/10. Independent review found no blocking findings and verified the repository settings and active ruleset through read-only API calls. The committed implementation matches the applied protection. The T3 review transport did not write this PR record automatically.
Reviewed head: 3700e38. Base: 1958d75. Review session.
Non-blocking notes and dispositions:
(Written by GPT-6.1 Sol with xhigh)