[brettheap]

Lane: openreposhape-5 (openRepoShape-5)
Claim: #301 (comment)
Claim: #280 (comment)

Two reader-side defects the lane filed, in one commit (21fbea4) on fix/yaml-flow-brackets-surrogates, cut from main c7c02fa.

What changed

#301, scripts/repo_shape.py. In YAML a plain scalar inside a flow collection ends at any of [ ] { } ,. _split_flow counts brackets to find its commas and never asked whether the count went below zero or ended above it, so a stray bracket was kept as text:

• pins: [a, b]] read ['a', 'b]'];
• k: [x [a, b]] read ['x [a, b]'];
• since repo_shape.py: a quote opens a quoted scalar only where one begins and must close there, so k: [it's, a] reads two items, k: it's fine # note drops its comment, and an unclosed "abc or a mid-key [ is refused, not misread (#249, #250) #284, k: {a"]:} read the key a"].

PyYAML refuses each. A new _refuse_flow_indicator refuses a PLAIN item or value (called from _flow_value) and a PLAIN key (called from _split_key_flow) of a flow collection that holds [, ], { or }. The refusal is a YamlError, so load_yaml turns it into REFUSED yaml-unparsable and names the scalar: a plain scalar in a flow collection holds `]`, which ends it in YAML: 'b]'. These still read as before:

• a quoted scalar's brackets (k: ["a]", {"b}": "c]"}]);
• nested and empty flow collections;
• a bracket in a BLOCK plain scalar (k: a[b], - see [1]);
• a bracket in a comment after a flow.

No other function changed.

#280, templates/assembly-root/scripts/validate-manifest.py. _name_finding now reports a display name holding any of U+D800 to U+DFFF as manifest-name:

FINDING manifest-name: name is 'a\ud83db', which holds U+D83D, a lone surrogate: no UTF-8 file, commit message or console can hold it. Write each character as itself, or as one `\U` escape (`\U0001F600`, not the pair `\uD83D\uDE00`).

The finding goes to stderr with the name escaped by repr, before the manifest ok line could raise.

Why the #280 refusal is in the validator and not in the reader

The brief offered two places. The evidence rules out the reader:

• The writer emits these escapes on purpose. double_quoted('caf\udce9') is "caf\udce9". That is how adopt-project.py's plan keeps a path byte that is not UTF-8 (adopt-project.py plan writes a plan its own loader cannot parse when a source name holds a line break (the macOS Icon\r file), so check refuses the whole plan as yaml-unparsable with no entry to edit #199), and check must read it back. tests/test_adopt_entry_paths.py holds that round trip (120 passed with test_adopt_plan.py on this head). Lane 1's pending An adopted assembly records nothing about which leg a human chose for a source submodule, so shape-doctor.py cannot verify a kept gitlink's placement and can only note it; adopt should write the plan's submodule answers into the assembly #189 branch (70f4d29, submodule_record) also writes \udce9 escapes into project.yaml's submodules: block, and its docstring relies on the reader resolving them. A reader refusal would break both.

• PyYAML 6.0.3 agrees with the reader. The pure-Python SafeLoader reads name: "a\ud83db" as the lone surrogate. Only libyaml (CSafeLoader) refuses it, and it refuses even the escape pair "\ud83d\ude00", which the Python loader reads as two surrogates, as this reader does.

• The defect is in a value, not in the YAML. A display name is text a person chose, and no UTF-8 stream holds a surrogate. On c7c02fa (probe280.py, local bare remotes only):

  launcher	c7c02fa	21fbea4
  scripts/validate-manifest.py	exit 1, UnicodeEncodeError traceback	exit 1, the manifest-name finding
  make validate	exit 2 on that traceback	exit 2 on the finding
  shape-doctor.py --root .	INVALID (manifest), the row quotes UnicodeEncodeError: ...	INVALID (manifest), the row quotes FINDING manifest-name: ...
  a real bump-leg.py	exit 0, prints manifest ok: a\ud83db, and COMMITS the subject Bump spec leg to <sha> in a?b (errors="replace")	exit 2 bump-leg-validators-red, every byte rolled back, 0 commits
  update-shape.py apply	exit 0, prints manifest ok: a\ud83db, commits	exit 2 update-validators-red, restored, 0 commits

So all four launchers now agree, and each names the problem.

Readers and callers this changes

• repo_shape.py: a flow collection with an unmatched ] or } is read, not refused, so k: {a"]:} reads {'a"]': None} since #284 (a quote toggle used to swallow the :}) and k: [a]] reads ['a]'], where PyYAML refuses both #301: every parse_yaml/load_yaml caller, and only for a document whose flow collection holds a plain scalar with a bracket. Such a document was read, or misread, before and is refused now. Every tracked YAML file loads the same on c7c02fa and on this head (14/14 raw, 18/18 rendered templates). So do the 6 YAML files of a scaffolded project (project.yaml, four contracts/*.yaml and validate.yml): 6/6 on a c7c02fa scaffold and 6/6 on a 21fbea4 scaffold. No writer emits such a scalar:

  • every flow sequence written in the tree is bare names or [] (adopt's pins: [...] and allow_empty_legs: [...], naming_block's also_matches and referent_chain);
  • double_quoted quotes any value holding a bracket.

• validate-manifest.py accepts a display name holding a lone surrogate (name: "a\ud83db") and then raises UnicodeEncodeError printing it, so make validate and shape-doctor.py fail on a traceback instead of a finding while bump-leg.py and update-shape.py apply pass the same project once #254 lands #280: the project's own scripts/validate-manifest.py (a digest-pinned shape copy; it reaches existing projects through update-shape.py apply, which reports it upstream-changed). Every caller of that copy now stops at the finding:

  • make validate;
  • the CI step in validate.yml;
  • shape-doctor.py's manifest row;
  • bump-leg.py and update-shape.py apply (their red-validator refusal and rollback);
  • a family holder's make validate, which runs each member's.

  bootstrap.py runs the same copy in its step (b), but on such a name it dies at its own first print, before step (b) (see Left out).

  With scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314 merged as well, the scaffold's pre-check asks this validator about --name. In the tree of this head and scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314 alone, scaffold-project.py --name $'caf\xe9' --dry-run is refused scaffold-manifest-invalid with this finding before anything is created (checked at scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314's head 4b8da3d). On origin/main, where scaffold-project.py: --elected-by, --reference, --name and the elector's fallback are refused before anything exists when no file can hold them, so a byte that is not UTF-8 no longer creates repositories before a traceback (#282) #351 has landed and scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314 has not, that --name is already refused, as scaffold-unwritable-value.

Evidence

• Issue rows. All ten repo_shape.py: a flow collection with an unmatched ] or } is read, not refused, so k: {a"]:} reads {'a"]': None} since #284 (a quote toggle used to swallow the :}) and k: [a]] reads ['a]'], where PyYAML refuses both #301 documents reproduce on c7c02fa and are refused on this head. 8 are documents PyYAML refuses. 2 (k: {a:}#}: b}, k: {}#":}) PyYAML reads only by taking a # with no space before it for a comment, and they are refused by design, as k: "a"#c is. Every validate-manifest.py accepts a display name holding a lone surrogate (name: "a\ud83db") and then raises UnicodeEncodeError printing it, so make validate and shape-doctor.py fail on a traceback instead of a finding while bump-leg.py and update-shape.py apply pass the same project once #254 lands #280 row is in the table above.

• Seeded oracle fuzz (fuzz_oracle.py). Corpus: reviewA's, seed 2490250, 785,646 documents in six contexts. PyYAML 6.0.3 is the oracle only.

  	c7c02fa	21fbea4
  read the way PyYAML reads it	254,629	254,629
  read, where PyYAML refuses	179,999	112,562
  refused, where PyYAML reads	48,434	49,492
  read, but not as PyYAML reads it	2,330	1,272
  the flow contexts alone: read where PyYAML refuses / refused where PyYAML reads	77,073 / 15,413	10,306 / 16,465

  Only two kinds of document change:

  • 67,437 invalid documents c7c02fa read are refused;
  • 1,058 documents c7c02fa MISREAD are refused. 1,037 of these are PyYAML's # leniency, and 21 are a single-pair mapping in a flow sequence (k: [a:[]]), which the subset never read as a mapping.

  Nothing c7c02fa read correctly changes, nothing is newly read, and there are 0 crashes. Against the issue's two-line depth < 0 sketch, run on the same corpus, this head refuses everything the sketch refuses, plus 21,631 more: 21,608 invalid documents (the opener class, such as k: [a[] and k: [x [a, b]]) and 23 misreads. The fuzz ran on 38738cf, whose scripts/ and templates/ are byte-identical to 21fbea4's.

• Tests fail on c7c02fa. With the four test files copied onto c7c02fa: 45 failed, 191 passed. The failures are 31 bracket rows, 10 validator rows and the 4 launchers.

• Mutation probes. Each hunk was reverted or weakened on its own, and each mutant fails new tests:

  • M1, no check on items and values: 23 failed;
  • M2, no check on keys: 8;
  • M3, no quoted-scalar exemption: 14;
  • M4, no quoted-key gate: 11;
  • M5, closers only: 3;
  • M6, no surrogate finding: 10;
  • M7, upper bound excludes U+DFFF: 2;
  • M8, lower bound excludes U+D800: 2.

Tests

• New: tests/test_yaml_flow_brackets.py, with the ten issue rows, sixteen more positions, the refusal's wording, a file refusal, fifteen still-read rows and the writer round trip.
• In tests/test_manifest_validator.py: five surrogate spellings, each under a pipe and under PYTHONIOENCODING=utf-8, plus four still-ok controls on either side of the range.
• In tests/test_validator_child_encoding.py: a real bump, update-shape.py apply, the doctor and make validate, each on name: "a\ud83db".
• tests/test_yaml_quote_boundaries.py: its docstring said k: "a"#c was the only PyYAML disagreement. There are eight; seven are BRACKET_IN_A_KEY rows refused by design (repo_shape.py: a flow collection with an unmatched ] or } is read, not refused, so k: {a"]:} reads {'a"]': None} since #284 (a quote toggle used to swallow the :}) and k: [a]] reads ['a]'], where PyYAML refuses both #301's NIT-A).

Targeted runs on 21fbea4, Linux, Python 3.12.3, git-filter-repo 2.47.0, each in the background:

• the reader and validator files (test_yaml_flow_brackets, test_yaml_flow_quotes, test_yaml_flow_mappings, test_yaml_quote_boundaries, test_yaml_block_scalar_keys, test_load_yaml_refusals, test_adopt_plan_escapes, test_manifest_validator, test_pin_validator, test_neutral_pin_validator, test_template_quoted_values): 462 passed;
• test_validator_child_encoding, test_stdout_encoding, test_repo_hygiene, test_cli_reference: 165 passed, 1 skipped (test_stdout_encoding.py:286, a Windows-only default);
• test_adopt_plan, test_adopt_entry_paths: 120 passed, 1 skipped (test_adopt_plan.py:393, SHAPE_MEDXEHR_CLONE unset);
• test_shape_doctor: 242 passed, 3 skipped (test_shape_doctor.py:5330, PowerShell on a Windows host only);
• this head merged with origin/main 86da808, which carries shape_materialize.py: render substitutes in one pass and refuses only a placeholder its table lacks, so --elected-by '{{SPEC_PATH}}' is no longer recorded as spec and {{NOPE}} no longer refuses after the legs are pushed (#260) #316: test_template_quoted_values, test_template_values_single_pass, test_yaml_flow_brackets, test_yaml_quote_boundaries, test_manifest_validator: 412 passed;
• this head merged with scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314 (ab66bc0): test_scaffold_manifest_values, test_adopt_manifest_values, test_manifest_validator, test_yaml_flow_brackets: 293 passed.

The full suite and the macOS and Windows legs were not run here.

Merge-tree (git merge-tree --write-tree --name-only)

Re-run at 2026-10-12T15:12Z, against origin/main d82a83e and the heads named here.

• Clean with this commit:
  • origin/main d82a83e, which carries shape_materialize.py: render substitutes in one pass and refuses only a placeholder its table lacks, so --elected-by '{{SPEC_PATH}}' is no longer recorded as spec and {{NOPE}} no longer refuses after the legs are pushed (#260) #316 (34ecbc2), adopt-project.py: a relative .gitmodules url the plan keeps in a leg is resolved from the source's remote and from the leg's, and where the two differ check finds it and execute refuses before any leg exists, so a recursive clone no longer fails after adoption verified (#190) #245 (head a0272b2, landed at 14:55Z as 161c6c9) and scaffold-project.py: --elected-by, --reference, --name and the elector's fallback are refused before anything exists when no file can hold them, so a byte that is not UTF-8 no longer creates repositories before a traceback (#282) #351 (landed as d82a83e). adopt-project.py: a relative .gitmodules url the plan keeps in a leg is resolved from the source's remote and from the leg's, and where the two differ check finds it and execute refuses before any leg exists, so a recursive clone no longer fails after adoption verified (#190) #245's one change to scripts/repo_shape.py is in remote_key, away from the YAML reader, and scaffold-project.py: --elected-by, --reference, --name and the elector's fallback are refused before anything exists when no file can hold them, so a byte that is not UTF-8 no longer creates repositories before a traceback (#282) #351 touches scaffold-project.py only;
  • scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314 (4b8da3d). With it merged, the --name refusal above still holds (checked at 4b8da3d);
  • lane 1's fix/adopt-late-failure-notice (9f1778d) and fix/adopt-plan-quote-yaml-keywords (d38e143);
  • the sibling fix/pin-source-env-collisions (34dbd86, scripts/repo_shape.py: pin_source_env_name turns every character outside [A-Z0-9_] into _, so the neutral products open-glass, open_glass and open.glass share one SHAPE_PIN_SOURCE_OPEN_GLASS, and a project that pins two of them gets a neutral-pin-source-unreadable FINDING (exit 1) for whichever one the variable does not name #275);
  • every other open PR head but one: 28 of the 29 open, all but shape-doctor.py: the manifest kinds row puts back a shape or leg pin under contracts/ that does not load with the git command pin_restore picks from its own state, shows a copy the shape pin has a row for or a neutral product pin with a read-only git diff, and leaves any other file to a person whatever it is called, so its NEXT no longer tells the reader to delete the pin (#291) #358.
• Conflicts that are not this commit's. Each conflicts the same way with origin/main alone, in a file this commit does not touch:
  • shape-doctor.py: the manifest kinds row puts back a shape or leg pin under contracts/ that does not load with the git command pin_restore picks from its own state, shows a copy the shape pin has a row for or a neutral product pin with a read-only git diff, and leaves any other file to a person whatever it is called, so its NEXT no longer tells the reader to delete the pin (#291) #358 (ebffb08), in shape-doctor.py;
  • lane 1's fix/adopt-root-kept-symlinks (6c44591), in adopt-project.py.
• Five heads already conflict with origin/main itself, and merge clean with this commit: scaffold-project.py and adopt-project.py ask the project's YAML reader and validate-manifest.py about the manifest's values before anything exists, so --id null, --tracking-branch true and a blank --elected-by are refused (#258, #261) #314, adopt-project.py: check finds, and execute refuses before any leg exists, a plan follow_ups: that is not a list of text and an elected_on: that election_date does not read, with or without a reference:, so follow_ups: 5 is no longer a traceback and elected_on: someday is no longer refused under a flag neither command takes (#293, #294) #356 (5a5011d), adopt-project.py: check reports the split branch an earlier run left as execute's adopt-branch-exists, and a branch in git's way of it as plan-split-branch-taken, which execute now refuses before any leg exists, so a source branch adopt no longer has both legs made before git filter-repo fails (#320) #382 (7e55d00) and lane 1's fix/adopt-plan-quote-yaml-keywords in adopt-project.py, and lane 1's fix/adopt-late-failure-notice in tests/conftest.py.
• One conflict is this commit's: fix/adopt-record-submodule-placement (70f4d29, lane 1, An adopted assembly records nothing about which leg a human chose for a source submodule, so shape-doctor.py cannot verify a kept gitlink's placement and can only note it; adopt should write the plan's submodule answers into the assembly #189), in one hunk, the import block of tests/test_manifest_validator.py. Both branches add to it: that branch adds import os and import sys, and this one adds import subprocess between them, so the resolution is all three. Its repo_shape.py and validate-manifest.py changes auto-merge. Not resolved in either branch.

Review

An independent opus review at 21fbea4 approved it with nits: 0 blocker, 0 should-fix, 5 nit. All five are in text (this body, the writer's report and the commit message), none in the code or the tests. Four are fixed in this body; the fifth, the commit message's spelling of the surrogate escape, is for the squash message. Its own seeded structured fuzz (seed 7301280: 120,000 nested flows in five block contexts, 600,000 documents, PyYAML 6.0.3 as the oracle only) found 0 changed reads: no document c7c02fa read the way PyYAML reads it changed, and nothing crashed. An instrumented reader returned no plain scalar holding [ ] { } inside a flow on this head, against 76,955 on c7c02fa. The writer's seed 2490250 counts reproduced row for row, and all 13 mutants it tried were killed. 664 passed on this head merged with origin/main ab623dd (16 test files; 361 on the head alone, 8 files). The one conflict, with lane 1's #189 branch, is the tests/test_manifest_validator.py import block, and resolves to all three imports. Three follow-ups it confirmed are not in this change: the bootstrap's raw name print and the flow entries still read (both under Left out), and a block value that opens with ] or }, which c7c02fa and this head both read where PyYAML refuses.

Left out

• A plain flow entry that opens with an indicator, and an empty flow entry. Most of what this head still reads where PyYAML refuses is one of two classes:

  • an entry opening with :, #, ? or - (k: {:":} reads {':"': None}, k: [:]; 6,286 flow documents);
  • an empty entry from a leading or doubled comma (k: [,a] reads ['a'], k: [a,,b] reads ['a', 'b']; 3,858).

  Neither is a bracket, and repo_shape.py: a flow collection with an unmatched ] or } is read, not refused, so k: {a"]:} reads {'a"]': None} since #284 (a quote toggle used to swallow the :}) and k: [a]] reads ['a]'], where PyYAML refuses both #301 does not claim them.

• A single-pair mapping in a flow sequence. k: [a: b] still reads as the string 'a: b', where PyYAML reads [{'a': 'b'}]. Only the ones holding a bracket are now refused.

• templates/assembly-root/scripts/bootstrap.py. It prints the display name raw (bootstrap: <name> (<root>)) before its validators run. On a project named "a\ud83db", make bootstrap still dies there with UnicodeEncodeError, on c7c02fa and on this head.

• elected_by and reference. A surrogate in either is still accepted. Neither is printed by the validator, so nothing raises; the scaffold side of such values is scaffold-project.py writes --elected-by, --reference and --name between literal double quotes with no escaping and asks none of them whether a file can hold it, so a line break leaves a project.yaml its own validators refuse, a backslash is recorded as another character (CORP\nick as CORP, a line feed, ick), and a byte that is not UTF-8 dies in write_lf after the legs are pushed #282.

• The escape pair "\ud83d\ude00". It is still two surrogates, not one character, as PyYAML's Python loader reads it. The finding asks for the character itself or its one \U escape instead of the reader inventing a joining rule.

Closes #301
Closes #280

🤖 Generated with Claude Code

Summary by Sourcery

Refuse ambiguous flow YAML and surface invalid manifest names consistently across validation tools.

Bug Fixes:

• Reject plain scalars containing flow-collection bracket indicators instead of silently misreading malformed YAML.
• Report manifest display names containing lone UTF-16 surrogates as validation findings instead of allowing validator output to fail with an encoding error.

Tests:

• Add coverage for malformed flow brackets, preserved valid bracket usage, writer round trips, surrogate-containing names, and validator/launcher behavior.

[brettheap]

(lane openRepoShape-5, 2026-10-12T15:19Z) @codex review

[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 8 hours and 10 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[sourcery-ai]

Reviewer's Guide

The PR hardens YAML parsing by refusing bracket-bearing plain scalars in flow collections, preventing both invalid-document acceptance and known misreads, and hardens manifest validation by reporting lone-surrogate display names as actionable findings so all validator callers fail cleanly rather than crashing or committing corrupted output.

Flow diagram for YAML flow-scalar validation

flowchart TD
    A[Parse flow collection] --> B{Scalar is quoted?}
    B -->|Yes| C[Parse brackets as text]
    B -->|No| D{Contains [, ], {, or }?}
    D -->|No| E[Parse plain scalar]
    D -->|Yes| F[Raise YamlError]
    F --> G[load_yaml returns REFUSED yaml-unparsable]

Loading

Flow diagram for manifest surrogate validation

flowchart TD
    A[Read manifest name] --> B{Non-empty string?}
    B -->|No| C[Return manifest-name finding]
    B -->|Yes| D{Contains U+D800 to U+DFFF?}
    D -->|No| E[Continue validation]
    D -->|Yes| F[Return manifest-name finding with escaped name]
    C --> G[Validator caller fails cleanly]
    F --> G[Validator caller fails cleanly]
    G --> H[Prevent UnicodeEncodeError or corrupted commit]

Loading

File-Level Changes

Change	Details	Files
Reject bracket-bearing plain scalars inside YAML flow collections instead of silently misparsing them.	Added centralized detection for [, ], {, and } in plain flow items and values. Applied the same refusal to plain flow mapping keys while preserving quoted scalars, block scalars, comments, nesting, and empty collections. Raised YamlError with the offending indicator and scalar so callers report yaml-unparsable with useful context. Added issue/regression, boundary, file-level refusal, and writer round-trip coverage.	scripts/repo_shape.py tests/test_yaml_flow_brackets.py tests/test_yaml_quote_boundaries.py
Turn display names containing lone UTF-16 surrogates into validator findings before output encoding can fail.	Detect the complete U+D800–U+DFFF range and report the first surrogate using an escaped repr and code point. Keep valid neighboring code points and ordinary astral \U escapes accepted, while explaining that surrogate pairs remain invalid. Add direct validator tests under pipe and UTF-8 output settings. Exercise validator consumers, rollback behavior, shape doctor reporting, and make validate to ensure they stop cleanly without tracebacks.	templates/assembly-root/scripts/validate-manifest.py tests/test_manifest_validator.py tests/test_validator_child_encoding.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#280	Make the manifest validator handle a display name containing a lone surrogate consistently, either by rejecting it with a named finding or by safely printing it.	✅
#280	Exercise the surrogate-name case through make validate, shape-doctor.py, a real bump-leg.py, and update-shape.py apply.	✅
#301	Refuse malformed flow collections when a plain flow scalar contains a bracket or brace that YAML treats as a collection boundary, including unmatched closers and openers within plain items, keys, or values.	✅
#301	Add regression coverage for the reported malformed-flow cases and correct the quote-boundaries test docstring's count of PyYAML disagreements.	✅

Possibly linked issues

• repo_shape.py: a flow collection with an unmatched ] or } is read, not refused, so k: {a"]:} reads {'a"]': None} since #284 (a quote toggle used to swallow the :}) and k: [a]] reads ['a]'], where PyYAML refuses both #301: The PR refuses plain flow scalars containing brackets, covering the issue’s unmatched-closer examples and related opener cases.

---

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.

[sonarqubecloud]

Quality Gate passed

Issues
3 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