docs: flake-vs-regression triage + git show cross-branch reads#101
Merged
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation for git workflows and merge gate monitoring. It adds a guide on reading files from the object store using 'git show' and provides criteria for distinguishing between infrastructure flakes and real regressions in sharded test suites. The review comments suggest clarifying the scope of 'git diff' for file comparisons and refining the definition of 'real regressions' to better accommodate single-shard Playwright failures.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
CybotTM
added a commit
that referenced
this pull request
Jul 16, 2026
…tion Gemini review on #101: `git diff <A> <B> -- <path>` compares a file, not the whole tree — reword and add `-- <path>` to the three-dot example. And the "real regression fails across all shards" line tensioned with the single-shard Playwright case — mark it the typical case, with the Playwright exception. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
CybotTM
added a commit
that referenced
this pull request
Jul 16, 2026
…tion Gemini review on #101: `git diff <A> <B> -- <path>` compares a file, not the whole tree — reword and add `-- <path>` to the three-dot example. And the "real regression fails across all shards" line tensioned with the single-shard Playwright case — mark it the typical case, with the Playwright exception. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
CybotTM
force-pushed
the
feat/retro-shard-triage-and-git-show
branch
from
July 16, 2026 20:27
3679e6e to
32d6147
Compare
…ession A /retro session (2026-07-16) found a red `E2E (1/4)` dismissed as a boot flake twice — correct once, but the second run was a real regression. Add a section on reading the shard's first error: a stack-boot/health-check line at the top means collateral failures below (infra flake, rerun); the same specs failing across all shards means a real bug. Notes the Playwright `locator.check: Test timeout` = actionability tell for a broken hit target. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
Add `git show <branch>:<path>` for inspecting a file's committed content on another ref without checkout. A /retro session (2026-07-16) hit a phantom "file was modified" after a branch switch — the on-disk copy reflected the landed branch, not the one being reasoned about. Reading from the object store is authoritative. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
…tion Gemini review on #101: `git diff <A> <B> -- <path>` compares a file, not the whole tree — reword and add `-- <path>` to the three-dot example. And the "real regression fails across all shards" line tensioned with the single-shard Playwright case — mark it the typical case, with the Playwright exception. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
CybotTM
force-pushed
the
feat/retro-shard-triage-and-git-show
branch
from
July 16, 2026 20:31
32d6147 to
824f8d8
Compare
|
CybotTM
enabled auto-merge
July 16, 2026 20:31
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.
Summary
Two reference additions from a
/retrosession: how to tell a one-shard-red CI failure apart (flake vs. real regression), and reading a file as committed on another branch without checkout.Came from
/retrosession on 2026-07-16 (timetracker release/deploy work).E2E (1/4)was dismissed as a boot-flake twice; the second run was a real regression a.field-check-rowrestyle had introduced (a spec'sgetByText-anchored.check()hung 30s). Separately, a phantom "file was modified" reminder after a branch switch nearly sent me chasing a non-edit.git checkoutinstead of the object store.locator.checktimeout = actionability regression). Usegit show <branch>:<path>to read committed state across branches.Change
merge-gate-watcher.md: new "One shard red: flake vs. real regression" section.advanced-git.md: new "Reading a File As It Is Committed on Another Branch" section.Test plan
Build/Scripts/validate-skill.sh— 0 errors, 0 warningsgit show <ref>:<path>,git diff A B -- path,gh run rerun <id> --failed)