Repository navigation
UPSTREAM.md: three rows it missed, and upstream reviewed again - #90
Merged
Merged
Conversation
The table of what upstream does not have stops at the shallow-clone refusal. Three later changes a user of the command can see have no row: QUIET in the environment no longer quiets it (#81), errors say what was being done (#83), and a run can be stopped (#86). Upstream's main is still the commit forked from: the comparison of a8d4555 with main, asked of GitHub today, is zero commits ahead. The "Reviewed through" line takes today's date. For #50. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: closer-claudio <claudio@farcloser.world>
closer-claudio
enabled auto-merge
November 16, 2026 03:02
Author
|
Reviewed at 287ce0f |
1 similar comment
Author
|
Reviewed at 287ce0f |
apostasie
approved these changes
Nov 16, 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.
🎯 Why
UPSTREAM.md's table of what upstream does not have stops at the shallow-clone refusal. Three later changes that a user of the command can see have no row.🛠️ What
UPSTREAM.md:QUIETin the environment no longer quieting the command (QUIET in the environment no longer quiets git-validation, only -q; the validate package prints no report: NewRunner loses its verbose argument and Runner.Report receives each commit's results #81);mainis still the commit forked from,a8d4555.🧪 How
a8d4555with upstream'smain, asked today, is zero commits ahead.V:
just lintandjust testgreen on the branch.📝 Notes
For #50.