fix(web): a merged pull request wraps up its thread once, and a setting can turn that off - #225
Merged
Merged
Conversation
…ng can turn that off A thread whose pull request merged was filed under Wrapped again after every turn, because the sidebar only knew the pull request was merged and not when. The row also kept the branch the thread began on after its worktree moved, so it stayed linked to the old, merged pull request. Listings now carry when a pull request landed, and the sidebar files a thread only while nothing has come from the user since: a later message, or a later keep-active, brings it back until the next landing. A thread that owns a worktree records the branch the worktree is on, so its badge follows the new pull request. A new switch under Settings, Projects & Threads, turns the automatic wrap-up off.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
vouch:trusted
badcuban
enabled auto-merge
September 5, 2026 07:01
badcuban
disabled auto-merge
September 5, 2026 07:57
badcuban
enabled auto-merge (squash)
September 5, 2026 07:57
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
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.
A thread whose pull request merged was filed under Wrapped again after every turn, because the sidebar only knew the pull request was merged and not when. The row also kept the branch the thread began on after its worktree moved, so it stayed linked to the old, merged pull request.
Listings now carry when a pull request landed, and the sidebar files a thread only while nothing has come from the user since: a later message, or a later keep-active, brings it back until the next landing. A thread that owns a worktree records the branch the worktree is on, so its badge follows the new pull request. A new switch under Settings, Projects & Threads, turns the automatic wrap-up off.