Repository navigation
Adopt the PR and CI tools in the adapter - #94
Merged
Merged
Conversation
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.
Adopts the five opportunities listed in #93 in
t3-adapter.md, Pull requests section, and bumps the plugin to 0.17.2. No upstream file changes, sodrift.jsonis untouched.What changed
pull_request_updatehas no base parameter, so Shipping's retarget to trunk stays ongh pr edit --baseororigin pr edit --base.PASS,PASS+NOTES, orFAILwithpull_request_reviewandverdict: "comment", with findings as line comments. It never approves or requests changes, because T3 agents act as the user's forge account.pull_request_mergewithmethod: "squash"and the fullexpectedHeadShathe verdict covers. A run on a native GitHub stack lands in one call on the ceiling withstack: true. T3 pins lower layers to their current heads, not to their verdicts, so step 3's check runs on every layer first. A derived stack merges one PR at a time, because T3 refusesstackthere. Auto-merge isauto: trueunder step 4's rule, never withstack. A resultstateofopenmeans queued, andpull_request_readconfirms the landing.pull_request_readconversationand answered withpull_request_respond. Only a bot's thread is resolved, and only once the reply cites the fixing commit or a disproof. Failing checks are read withci_logs, and a flake's one fresh build isci_rerunon that check.O1 in #93 named autopilot-stack too. That playbook never merges, so only Shipping uses
stack: true.Facts taken from T3 at
59651c1: the merge handler'sstackMergeScope(rejectsauto, requires a host stack, pins lower layers to host heads) anddocs/user/source-control.md(GitHub stacks).Checks
bun run check,bun test tools(40 pass), andbun run typecheckpass.