[brettheap]

U037 is the last item of #915. A --reuse-empty-repo re-run turns off git's own terminal prompt and no other prompt, so ssh, a credential helper or an askpass program can still make it wait. This PR says so in the places where it is true, and says how a person keeps a run from waiting. It changes nothing that a run does.

The ruling

Brett Heap, 2026-10-21T10:39:44Z: "U039 and U037: take your recommendations". For U037, lane 3 recommended leaving the operator's own ssh, credential-helper and askpass setup alone, and saying where a prompt can still come.

Why the environment stays the operator's:

• Credential helpers and askpass programs are how people give git a login. Turning them off would refuse reads and pushes that work today.
• ssh's BatchMode is not forced through GIT_SSH_COMMAND. git's GIT_SSH_COMMAND overrides a configured core.sshCommand, so forcing it would replace the operator's own ssh command (a key given by -i, a proxy, a port). This was measured below: with both set, only GIT_SSH_COMMAND ran.

Measured before writing, at main 2a119f2

Each case ran scaffold-project.py --reuse-empty-repo in its GitHub mode against the tests' fake gh, with the stub gh behind it, GH_TOKEN=bogus, an empty GH_CONFIG_DIR, GIT_CONFIG_GLOBAL set to a scratch file and no ssh agent. Each ran in a pseudo-terminal (the tests' run_in_a_terminal) and was killed after 20 s. git read https://github.com/testorg/ through an insteadOf rule, either from fakehost.invalid: or from a local HTTP server that answers 401. No real host was reached. The real ssh reached a fake server on stdio through a ProxyCommand, and that server does just enough key exchange to reach the client's host-key check.

case	git reaches the leg through	result
t0 probe	http 401, no helper, no askpass	refused at once (1.6 s): could not read Username for '...': terminal prompts disabled
t1 probe	real OpenSSH 9.6p1, unknown host key	waited at Are you sure you want to continue connecting (yes/no/[fingerprint])? until killed
t1 push (all three empty)	same	waited at the same prompt until killed
t1 probe	fake GIT_SSH_COMMAND that asks the tty for a passphrase	waited at Enter passphrase for key ... until killed
t1 push	same	waited until killed
t2 probe	a credential helper that asks the tty	waited until killed
t2 push	same	waited until killed
t3 probe	GIT_ASKPASS	waited at Fake askpass: Username for 'http://127.0.0.1:...' until killed
t4 probe	SSH_ASKPASS, with no GIT_ASKPASS	waited until killed
t5 probe	core.askPass	waited until killed
t6 probe	real ssh with GIT_SSH_COMMAND='ssh -o BatchMode=yes ...'	refused in 1.3 s: scaffold-remote-exists, reason Host key verification failed.
t6 push	same	refused in 3.2 s
override	core.sshCommand and GIT_SSH_COMMAND both set	only GIT_SSH_COMMAND ran

git passed ssh no BatchMode. The argv was -o SendEnv=GIT_PROTOCOL fakehost.invalid git-upload-pack 'testorg/Atlas-spec.git'. Lane 2's probes t1 to t5 at fdb0fa5 (L2-21) were the earlier evidence.

What changed

• scaffold-project.py. Words only, plus local passed to _exists_remedy so the words appear only where a prompt can follow:
  • The comment over REMOTE_ENV now records the ruling, and why the environment stays the operator's. It replaces the open question the comment held before.
  • PROMPTS_STILL_ASK is one sentence. Each remedy whose exit is the --reuse-empty-repo re-run now ends with it: _exists_remedy's for a leg git could not read, for an empty leg or one holding the seed, and for an empty root, and _login_remedy's. The sentence reads: "That re-run turns off git's own terminal prompt and no other, so it can still wait at an ssh passphrase or host-key prompt, at a credential helper that prompts, or at GIT_ASKPASS, SSH_ASKPASS or core.askPass: to keep it from waiting, load your key into an ssh agent, use a helper that answers without prompting, or set GIT_SSH_COMMAND='ssh -o BatchMode=yes' (with anything your core.sshCommand adds) in your shell for the run, which makes ssh fail at once instead."
  • The --reuse-empty-repo help says the same in the third person, of a run on GitHub.
• docs/cli.md is regenerated by scripts/render-cli-reference.py. Only the scaffold's --reuse-empty-repo entry moved.
• README.md and docs/handbook.html say it where the re-run is described, in "Starting a project in a new organisation" and the handbook's matching list. The handbook's seven markers for that README section now carry its new blob, ffaedeefe617.
• tests/readme-cap.d/915.txt records the seven README lines. The README was at its cap of 1482.
• tests/test_scaffold_reuse_seeded_legs.py:
  • STILL_ASKS, a literal, is now part of UNREAD_EXIT, RE_RUN_WITH_THE_FLAG and RE_RUN_AS_IT_WAS.
  • The new test test_each_re_run_remedy_says_the_prompts_it_can_still_wait_at covers six remedies, in-process. Each remedy whose exit is the re-run ends with the sentence on GitHub. The remedy for a leg with other commits and the one for a root with commits do not, and no remedy carries it under --local-remote-dir.
  • The local empty-leg refusal now asserts the sentence is absent.

Decisions the Direction left open:

• Which refusals say it. Only the remedies whose exit is the re-run. A remedy that sends a person to delete a leg or to adopt a root does not. Under --local-remote-dir, git reads paths on disk with no ssh, helper or askpass, so no prompt can follow there.
• Where in a refused push. Only the login remedy says it. A push refused for any other reason (a ruleset's refusal, an HTTP 403) still prints exactly what it always printed, which test_what_a_refused_push_prints pins.
• The GIT_SSH_COMMAND advice. It says "with anything your core.sshCommand adds", because setting it replaces that setting for the run.
• setup-project.py. Unchanged. Its help never names --reuse-empty-repo: it passes anything after -- to the scaffold, and the scaffold's remedies already say "(after -- through setup.sh)".
• AGENTS.md. It is at its line cap, so no line was added there.

Left out of scope

• RULESET_HINT in scripts/shape_materialize.py also sends a person into the re-run. That file is outside this task's files, so the hint does not say any of this. A push refused for any reason other than a login prints that hint alone after git's output. One measured case: ssh's Host key verification failed. under BatchMode=yes, on the branch. scaffold-project.py: the ruleset hint sends a person into the --reuse-empty-repo re-run without #915's prompt sentence, and a push refused for its ssh host key gets that hint alone #1108 follows this up, for both parts: the hint's prompt sentence on GitHub only, and a push refused for its host key getting the hint alone. The comments over REMOTE_ENV and PROMPTS_STILL_ASK name it.
• family.py init's own --reuse-empty-repo re-run is outside scaffold-project.py: a --reuse-empty-repo re-run can stop at a git, ssh or helper prompt on its pushes and seed fetch, and an ssh-rewrite operator's refusal gives git's generic line and a remedy that does not apply #915, which covers the scaffold.
• scaffold-project.py: a --reuse-empty-repo re-run can stop at a git, ssh or helper prompt on its pushes and seed fetch, and an ssh-rewrite operator's refusal gives git's generic line and a remedy that does not apply #915's U036 and U038 landed in scaffold-project.py: a first scaffold's pushes and a --reuse-empty-repo re-run's pushes and seed fetch no longer ask at the terminal: a push git has no login for fails naming the fix, and a leg git reaches over ssh is refused with ssh's reason (#915) #971, with scaffold-project.py: a push whose stored login GitHub rejects (fatal: Authentication failed) is refused with only the ruleset hint, where a push git has no login for is told how to give git one #993 after it.
• scaffold-project.py: a --reuse-empty-repo re-run can stop at a git, ssh or helper prompt on its pushes and seed fetch, and an ssh-rewrite operator's refusal gives git's generic line and a remedy that does not apply #915 has no "Needs a ruling" or "Documented limit" section. U037's ruling question is answered by the ruling above.

Tests

Each file was run alone with /usr/bin/python3 -m pytest -q -p no:cacheprovider --basetemp=<scratch>/bt-<name> -o tmp_path_retention_policy=failed tests/<file>, wrapped in timeout 2400. Each run had the stub gh (exit 97) first on PATH, GH_TOKEN=bogus, an empty GH_CONFIG_DIR, GIT_SSH_COMMAND=false, GIT_CONFIG_GLOBAL=/dev/null and EMAIL=tests@openreposhape.invalid.

file	result
tests/test_scaffold_reuse_seeded_legs.py	90 passed in 74.88s
tests/test_cli_reference.py	23 passed in 33.94s
tests/test_readme_sections.py	76 passed in 0.54s
tests/test_agents_md_codes.py	47 passed in 2.23s
tests/test_update_add_codes_documented.py	6 passed in 0.56s
tests/test_repo_hygiene.py	100 passed in 2.83s
tests/test_no_auto_maintenance.py	58 passed, 2 skipped in 15.20s
tests/test_readme_windows_quoting_sentence.py	44 passed in 19.27s
tests/test_dry_run_asks_remotes.py	32 passed in 12.92s

The two skips in test_no_auto_maintenance.py both come from line 222: "the session began with GIT_CONFIG_GLOBAL set, and its file includes that one". That is this harness's GIT_CONFIG_GLOBAL=/dev/null. CI runs those two.

pyflakes reported no new warning. scaffold-project.py has 0 before and after. The test file has the same 14 before and after, all present at main.

Mutants

Each mutant broke the change, ran the named test, and put the file back byte for byte.

mutant	killed by
M1: drop the new help sentence	test_cli_reference.py::test_every_python_tools_help_is_the_text_the_file_carries and ::test_the_committed_reference_is_what_the_generator_produces (2 failed)
M2: _exists_remedy says nothing (still = "")	test_each_re_run_remedy_says_the_prompts_it_can_still_wait_at (4 ids) and test_a_leg_git_cannot_read_is_refused_as_existing_not_as_a_failure (2 ids)
M3: _reusable_remotes does not pass local	test_an_empty_leg_without_the_flag_is_refused_naming_the_flag
M4: _login_remedy says nothing	test_what_a_refused_push_prints (9 ids)
M5: drop the README sentence	test_repo_hygiene.py::test_the_handbook_follows_the_readmes_outline (the stale marker)

No test notices if the handbook's list item is dropped. The handbook's prose is not pinned anywhere.

Merges

• git merge-tree --write-tree of the head 2cbf54b with origin/main 7e00834 is clean (tree 0f96d3bc325a). Main has touched none of these files since 2a119f2. At the first head, the merge with 16f9a0e was clean too (tree 9151e06d3b92).
• templates/assembly-root/project.yaml and templates/family-root/family.yaml: the comment above visibility: says it is the visibility the run asked for, and that a repository the run reuses keeps its own, where it said "this is all three repositories' visibility" (#913) #1102 touches only templates/ and its own test; merge-tree clean (its head 2de0721 with this head: tree c93cb0019b81).
• No other open PR touches these files (checked live: shape-doctor.py: a gitlink beside a .gitmodules the leg's index tracks and this disk lacks is named from the index's copy, which git reads, with its own way out that restores the file first (git restore .gitmodules), as #1080 names one beside other sections (#1093) #1109, tests: the bump-leg.py and family.py reachability rows tag a descendant of the commit --to names, so a tag above it reads as one that reaches it and a tag below it keeps the plain words, and --points-at for --contains no longer survives (#1019) #1107, adopt-project.py: under a one-byte locale such as Latin-1, check reads a plan written in UTF-8 whose source is there, asking the plan's UTF-8 bytes where the spelling as written names nothing, rather than refusing plan-source-gone (#1078) #1106, shape_materialize.py and the pinned AGENTS-shape.md: where the root keeps a GNUmakefile or a makefile, which GNU make reads first, the Makefile collision follow-up no longer says the shape's make targets arrive with the merge, and the pinned file says make reads the first of the three and the block reaches it only once that file holds it (#1048) #1105, shape_materialize.py: env_commit's docstring says the split commit's message spells a path byte that is not UTF-8 as _shown does, an escape, and no longer says it names it with a ? in its place, which #900 replaced (#1018) #1104, family.py: a failed remove's by-hand lines spell a leg mounted at a path that is not UTF-8 as a printf word of octal escapes ending in a slash, so git -C <member>/<leg> and submodule update -- <leg> typed in any POSIX shell name that leg (#1086) #1098, tests.yml: the full suite keeps its temporary files under runner.temp, not /tmp, so it runs on Ubuntu 26.04 and the tests job goes back to ubuntu-latest (#1096) #1097, adopt-project.py: check names what the clone's .git holds as git keeps refs, and asks a pin's file through the links the root keeps, so a link into .git or onto a pin's file is refused before any leg or adopted with the copy beside it (#904) #1091, shape_materialize.py, adopt-project.py and bump-leg.py: a tag a clone holds without its commit is one it cannot answer for, check says a commit it cannot ask was not asked, and a pinned product YAML 1.1 or 1.2 reads as no text is quoted (#912) #1090 and the family root's bootstrap.py: credential_advice and ended_on say a member's failed clone ends git's update with 1 before any checkout but a leg's lets it go on, and killed_said says git's update was itself killed, not that it went on (#1085) #1088).

Review round 1 (RV1101: READY, no MUST)

Head 2cbf54b, one commit on top of 2c6d51a:

• S1: "Left out of scope" names scaffold-project.py: the ruleset hint sends a person into the --reuse-empty-repo re-run without #915's prompt sentence, and a push refused for its ssh host key gets that hint alone #1108 for the RULESET_HINT gaps.
• N1: the comments over REMOTE_ENV and PROMPTS_STILL_ASK say RULESET_HINT, the ruleset's refusal, does not say it yet (scaffold-project.py: the ruleset hint sends a person into the --reuse-empty-repo re-run without #915's prompt sentence, and a push refused for its ssh host key gets that hint alone #1108).
• N2: the help says "A run with it on GitHub, like every run there, ...", since nothing prompts under --local-remote-dir. docs/cli.md is regenerated by scripts/render-cli-reference.py.
• N3: the handbook's item opens "The --reuse-empty-repo re-run, as every run, ...". README.md is unchanged, so its blob and the handbook's markers stand.
• N4: templates/assembly-root/project.yaml and templates/family-root/family.yaml: the comment above visibility: says it is the visibility the run asked for, and that a repository the run reuses keeps its own, where it said "this is all three repositories' visibility" (#913) #1102 is in "Merges".

M1, re-made against the new help (the sentence dropped), was KILLED by test_cli_reference.py::test_every_python_tools_help_is_the_text_the_file_carries and ::test_the_committed_reference_is_what_the_generator_produces. The file was restored and cmp found it identical to the saved copy.

Tests at 2cbf54b, one file at a time under the same harness:

file	result
tests/test_scaffold_reuse_seeded_legs.py	90 passed in 58.31s
tests/test_cli_reference.py	23 passed in 32.36s
tests/test_readme_sections.py	76 passed in 0.30s
tests/test_repo_hygiene.py	100 passed in 2.50s

Closes #915

Lane: openreposhape-3 (openRepoShape-3)
🤖 Generated with Claude Code

[sourcery-ai]

Reviewer's Guide

The PR documents that --reuse-empty-repo disables only Git's native terminal prompt, explains how SSH, credential-helper, and askpass prompts can still block, and provides operator-controlled ways to fail fast; it updates synchronized documentation and adds coverage ensuring the guidance appears only on applicable GitHub re-run remedies.

File-Level Changes

Change	Details	Files
Document the prompt behavior and non-blocking operator options for --reuse-empty-repo without changing runtime prompt handling.	Add shared help/remedy text explaining that only Git's terminal prompt is disabled and SSH, credential-helper, and askpass prompts may still wait. Recommend an SSH agent, non-interactive credential helper, or GIT_SSH_COMMAND='ssh -o BatchMode=yes', while preserving the operator's SSH configuration. Apply the guidance only to GitHub re-run paths; omit it for local disk remotes and remedies that do not re-run with the flag. Clarify in code comments why the environment is intentionally left under operator control.	scaffold-project.py
Propagate the new guidance through generated CLI and user-facing project documentation.	Regenerate the --reuse-empty-repo CLI reference. Add the warning and mitigation guidance to the README's failure/re-run instructions. Synchronize the handbook section and update its README blob markers.	docs/cli.md README.md docs/handbook.html
Pin the documentation-cap and validate that the handbook remains synchronized with the README.	Record the seven updated README lines in the cap fixture.	tests/readme-cap.d/915.txt
Add focused regression coverage for prompt guidance placement and exact remedy text.	Define the expected prompt-warning suffix and include it in re-run remedy expectations. Test all relevant leg/root remedies, including unread and seeded cases, while excluding non-re-run and local-remote paths. Retain existing help, README, refused-push, and CLI generation assertions.	tests/test_scaffold_reuse_seeded_legs.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#915	Apply a consistent, decided prompt rule to every remote git command the scaffold runs, including reused-leg and root pushes and the held-seed fetch.	❌	The PR explicitly changes no runtime behavior. It does not pass the existing prompt environment to the three uncovered commands, so those commands do not run under the same rule as the probe commands.
#915	Resolve whether remote probes and pushes must avoid waiting for input, while preserving operators’ credential setups and explaining how to prevent prompts if they may still occur.	✅
#915	When an unread remote fails through an SSH rewrite, preserve the specific SSH failure instead of Git’s generic refusal and give an SSH-key-appropriate remedy.	❌	The PR does not change unread-error extraction or the SSH-rewrite remedy. Its body says U038 landed in another PR, but that fix is not present in the supplied changes.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[brettheap]

(lane openRepoShape-3, 2026-10-21T12:46:44Z) Independent review (RV1101) of head 2c6d51a, U037 of #915. Verdict: READY. No MUST.

Measured at the head, in a pseudo-terminal, under a stub gh, with no real host reached:

• probe, fake GIT_SSH_COMMAND asking the tty: still waiting at "Enter passphrase" after 20s, killed.
• probe, credential helper asking the tty: still waiting after 20s, killed.
• probe, real OpenSSH through a ProxyCommand to a fake server, no BatchMode: waits at the host-key question, killed.
• the same with GIT_SSH_COMMAND='<fake ssh> -o BatchMode=yes': refused in 0.6s, scaffold-remote-exists, "Host key verification failed."; the push form refused in 1.7s.
  Each clause of the new sentence holds.

Tests at the head, one file at a time: test_scaffold_reuse_seeded_legs.py 90 passed; test_cli_reference.py 23 passed; test_readme_sections.py 76 passed; test_repo_hygiene.py 100 passed.
Mutants, each restored and checked with cmp: M1 (help sentence dropped) killed, 5 failed; M2 (_exists_remedy says nothing) killed, 8 failed; M4 (_login_remedy says nothing) killed, 21 failed.
Merges: clean with origin/main 16f9a0e (tree 9151e06d3b92) and with #1102 f7f596a (tree ee0e804bf80e). No other open PR touches these six files.
Body: closes [915], milestone v1.2.0, draft, Closes/Lane/robot at the end, no other closing keyword, nothing above U+007F but the robot.

SHOULD before landing:
S1. File a follow-up issue and name it in "Left out of scope". Closes #915 will close the only place it is recorded. Two parts:
(a) RULESET_HINT (scripts/shape_materialize.py:1189) sends a person into the --reuse-empty-repo re-run and does not say the prompt sentence. It is printed under --local-remote-dir too, so it needs a GitHub-only path, not just words.
(b) A push refused with "Host key verification failed." prints RULESET_HINT alone (measured with BatchMode=yes, which this PR now advises). The re-run it names fails the same way.

NIT:
N1. scaffold-project.py:529-532 and :554 say "each remedy that sends a person into that re-run"; RULESET_HINT does that and does not say it. Name it and the follow-up.
N2. The help and docs/cli.md say "A run with it, like every run, ... can still wait at an ssh ..."; not so under --local-remote-dir. Say "on GitHub".
N3. docs/handbook.html:1127: the new list item opens "That re-run" with its antecedent in the previous item. Say "The --reuse-empty-repo re-run".
N4. Body "Merges": add #1102 (templates only, merge-tree clean).

Checked and fine: appending a second sentence follows precedent (_exists_remedy's "There is no --force." and the ruleset sentence at main, the family switch -c remedy, #874's REF_RULE_WORDS). tests/readme-cap.d/915.txt is the established ledger (README 1482 -> 1489 = 1422 + 67). The handbook prose is held by the README blob markers, as everywhere else.

Lane 3's plan: S1 is filed as #1108, outside v1.2.0. W915, the writer, names #1108 in the body's "Left out of scope" and takes N1 to N4: N1 names RULESET_HINT and #1108 in the two comments, N2 says "on GitHub" in the help and regenerates docs/cli.md, N3 opens the handbook item with "The --reuse-empty-repo re-run", and N4 adds #1102 to the Merges section. RV1101 then checks the new head. #1101 stays a draft until it is READY, green and gated.

Lane: openreposhape-3 (openRepoShape-3)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[brettheap]

(lane openRepoShape-3, 2026-10-21T12:54:20Z) Independent review (RV1101) round 2 of head 2cbf54b. Verdict: READY. No new items.

• N2: the --reuse-empty-repo help now says "A run with it on GitHub, like every run there", which is true word by word. docs/cli.md is the generator's output (test_the_committed_reference_is_what_the_generator_produces passes).
• N1: the comments at scaffold-project.py:534 and :566-567 are true. RULESET_HINT is unchanged by this PR, and scaffold-project.py: the ruleset hint sends a person into the --reuse-empty-repo re-run without #915's prompt sentence, and a push refused for its ssh host key gets that hint alone #1108 names both gaps.
• N3: handbook.html:1127 opens "The --reuse-empty-repo re-run, as every run". It is true in place and reads well, and the README markers still hold it (the README is unchanged; test_repo_hygiene passes).
• S1 and N4 in the body: scaffold-project.py: the ruleset hint sends a person into the --reuse-empty-repo re-run without #915's prompt sentence, and a push refused for its ssh host key gets that hint alone #1108 is named with no closing keyword. closingIssuesReferences is [915]. Draft, v1.2.0, Closes/Lane/robot at the end, nothing above U+007F but the robot. templates/assembly-root/project.yaml and templates/family-root/family.yaml: the comment above visibility: says it is the visibility the run asked for, and that a repository the run reuses keeps its own, where it said "this is all three repositories' visibility" (#913) #1102 is in Merges.
• M1 (help sentence dropped): still killed, 5 failed. The file was restored and checked with cmp.
• Tests at the head, one at a time: test_cli_reference.py 23 passed; test_repo_hygiene.py 100 passed; test_readme_sections.py 76 passed.
• Merges: clean with origin/main 7e00834 (tree 0f96d3bc325a) and with templates/assembly-root/project.yaml and templates/family-root/family.yaml: the comment above visibility: says it is the visibility the run asked for, and that a repository the run reuses keeps its own, where it said "this is all three repositories' visibility" (#913) #1102 2de0721 (tree c93cb0019b81).

Lane 3's plan: #1101's landing pilot is armed on 2cbf54b, chained behind #1102's, and released now. After #1102 lands, it waits for tests and SonarCloud on this head, gates the predicted squash over the new main, takes the HOLD in turn under the rule that the first PR green and gated goes first, and lands. Follow-up #1108 stays outside v1.2.0.

Lane: openreposhape-3 (openRepoShape-3)

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 4 hours and 16 minutes by commenting @sourcery-ai review. Upgrade to get a review now.