chore(release): prepare public gittensory launch - #2
Merged
Conversation
This was referenced Jun 25, 2026
This was referenced Jun 28, 2026
This was referenced Jul 2, 2026
This was referenced Jul 7, 2026
Merged
18 tasks
This was referenced Jul 11, 2026
Closed
fix(rees): TypeError in safeCodeSpan -- non-string value reaches .replace() (13 Sentry events)
#5002
Closed
Merged
19 tasks
nghetienhiep
pushed a commit
to nghetienhiep/gittensory
that referenced
this pull request
Jul 16, 2026
… PR head SHA The screenshot-table gate's PRESENCE-mode check (evaluateScreenshotTableGate) was pure regex/string matching over the PR body with no tie to the PR's live head SHA, unlike the bot-capture evidence path in the same function. A before/after table pasted on an early push kept satisfying the gate forever, even after later commits shipped a real visual regression the table never pictured. Presence-mode now fingerprints the exact before/after evidence (the extracted image URLs) and correlates it to the head SHA it last satisfied the gate at. A later push carrying the identical, unedited evidence re-violates; genuinely new evidence (the contributor re-affirms after the push) or a successful bot capture on the new head clears it again. The checkpoint is persisted (mirrors visualCaptureSatisfiedSha's headSha-keyed write) via a new markPullRequestScreenshotTablePresenceSatisfied call in the maintenance planner, backed by a new pull_requests column/migration. Mirrored the same change into the loopover-engine twin copy of this file to keep engine-parity green, and added a regression test reproducing the audited two-push scenario (table passes on push JSONbored#1, then silently stays stale through push JSONbored#2 pre-fix).
13 tasks
This was referenced Jul 26, 2026
loopover-orb Bot
pushed a commit
that referenced
this pull request
Jul 30, 2026
…t the PR ahead of it (#9954) The wait comment named the immediate blocker and nothing else: Queued in the merge train behind #4, which touches overlapping work and was opened first. "Behind #4" and "behind #4 and six others" are very different waits, and a queue that will not say which one it is reads as a stall rather than a wait -- which is how it was read in practice. The information was already computed and thrown away: shouldWaitForOlderSiblings builds the full sorted list of viable overlapping older siblings and returned only viable[0]. It now returns the whole list, and the comment reports the position: Queued in the merge train at position 4, behind 3 overlapping PRs opened before this one (#1, #2, #3). The nearest is #1. The single-blocker wording is unchanged -- rendering a one-item queue as "1 PR ahead: #4" is noise. The queue inherits every eviction rule the blocker choice already had, which the tests pin: a draft, a conflicted PR, a manual-review hold and a non-overlapping sibling are all absent from it. A contributor must never be told they are behind PRs that are not actually in front of them. Closes #9952
This was referenced Jul 30, 2026
4 tasks
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.
Summary
What changed
Why
Validation
Notes