From 287ce0f4cf76a842446e49aa68a1570fdad48949 Mon Sep 17 00:00:00 2001 From: closer-claudio Date: Sun, 15 Nov 2026 18:55:11 -0800 Subject: [PATCH] UPSTREAM.md: three rows it missed, and upstream reviewed again 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 (https://github.com/forkcloser/git-validation/pull/81), errors say what was being done (https://github.com/forkcloser/git-validation/pull/83), and a run can be stopped (https://github.com/forkcloser/git-validation/pull/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 https://github.com/forkcloser/git-validation/issues/50. Co-Authored-By: Claude Fable 5.2 Signed-off-by: closer-claudio --- UPSTREAM.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/UPSTREAM.md b/UPSTREAM.md index 5ec0827..5f97dbc 100644 --- a/UPSTREAM.md +++ b/UPSTREAM.md @@ -3,7 +3,7 @@ Fork of https://github.com/vbatts/git-validation (`main`). - Forked from: [`a8d4555`](https://github.com/vbatts/git-validation/commit/a8d455533459b620fa656bad095b943e70cede9b), committed 2025-04-14 -- Reviewed through: [`a8d4555`](https://github.com/vbatts/git-validation/commit/a8d455533459b620fa656bad095b943e70cede9b), reviewed 2026-10-15 +- Reviewed through: [`a8d4555`](https://github.com/vbatts/git-validation/commit/a8d455533459b620fa656bad095b943e70cede9b), reviewed 2026-11-15 ## Incorporated @@ -27,3 +27,6 @@ Fork of https://github.com/vbatts/git-validation (`main`). | A `--run` name no rule has is refused, naming it and listing the rules there are, where it ran nothing and passed; a `message_regexp` value that does not compile is refused before any commit is read, with the regexp package's words, where it panicked on the first commit; the final count is of commits with a failing result, not of results; "using commit range" is logged at debug | https://github.com/forkcloser/git-validation/pull/24 | | The short-subject rule counts characters, not bytes, against its limits; a `--range` git cannot resolve is an error naming the range and the failed git command in a repository with its whole history, nothing validated | https://github.com/forkcloser/git-validation/pull/39 | | A `--range` git cannot resolve is an error in a shallow clone too, where it used to validate what the clone had from its oldest commit, so a depth of one passed the head commit alone; the error names the end the clone does not have and what to fetch (`fetch-depth: 0`, `git fetch --deepen` or `--unshallow`), and a shallow clone deep enough for the range runs as before | https://github.com/forkcloser/git-validation/pull/47 | +| `QUIET` in the environment no longer quiets the command; `-q` does | https://github.com/forkcloser/git-validation/pull/81 | +| Errors from git and from the file system say what was being done when they happened | https://github.com/forkcloser/git-validation/pull/83 | +| A run can be stopped: on an interrupt the git that is running is killed, no further commit is read, and the error says the run was stopped, where nothing could stop a git that hangs | https://github.com/forkcloser/git-validation/pull/86 |