docs: revamp README with feature showcase and auto-updating benchmarks by thomhurst · Pull Request #6430 · thomhurst/TUnit

thomhurst · 2026-07-16T10:55:03Z

Summary

Rewrites the README to actually showcase TUnit, and adds automation so the new benchmark table never goes stale.

README changes

Hero section: realistic test snippet followed by the actual failure output TUnit produces (expression capture + focused differs at member object diff) — all message formats verified against TUnit.Assertions.Tests.
Performance section: scenario × framework table (TUnit AOT / TUnit / xUnit v3 / NUnit / MSTest) populated from docs/static/benchmarks/latest.json, with an honest note that source generation trades a slightly slower build for faster runs.
Feature tour: data-driven tests, chained/custom assertions ([GenerateAssertion]), shared fixtures via ClassDataSource + IAsyncInitializer, parallelism control (DependsOn, NotInParallel, ParallelLimiter<T>), hooks, and TUnit.Mocks (previously just a table row).
Integrations: ASP.NET Core, Aspire, Playwright, and FsCheck snippets — all copied/adapted from real test code in this repo.
Added TUnit.FsCheck and TUnit.OpenTelemetry to the packages table; noted F#/VB.NET support.

Benchmark automation

New .github/scripts/update-readme-benchmarks.js renders the table between  markers from latest.json (skips NA cells, fails loudly if markers vanish).
speed-comparison.yml runs it after process-benchmarks.js and includes README.md in the existing weekly auto-PR, so the table refreshes with zero manual effort.

Verification

Ran the injection script locally — table populated with the committed 2026-07-12 results (visible in this diff).
Snippet syntax cross-checked against real usages: HasCount(n), Contains(predicate), .Because(...), [Before(Test)], IFoo.Mock()/Returns/WasCalled(Times.Once), ClassDataSource shared scopes, TestWebApplicationFactory<T>, AspireFixture<T>, PageTest, [FsCheckProperty].

Rewrites the README around what TUnit can actually do: hero snippet with real failure output, focused object-diff example, benchmark table vs xUnit/NUnit/MSTest, and sections for mocking, shared fixtures, custom assertions, and the ASP.NET Core/Aspire/Playwright/FsCheck integrations. The benchmark table lives between  markers and is regenerated weekly: a new update-readme-benchmarks.js step in the speed-comparison workflow rewrites it from latest.json inside the existing automated benchmark PR.

codacy-production · 2026-07-16T10:56:10Z

Not up to standards ⛔

🔴 Issues 2 minor

Alerts:
⚠ 2 issues (≤ 0 issues of at least minor severity)

Results:
2 new issues

Category Results

BestPractice 1 minor

CodeStyle 1 minor

View in Codacy

🟢 Metrics 12 complexity

Metric Results

Complexity 12

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer}
_{TIP This summary will be updated as you push new changes.}

claude · 2026-07-16T11:01:52Z

Code review

Reviewed the README rewrite, the new update-readme-benchmarks.js script, and the speed-comparison.yml workflow changes.

Verification performed: cross-checked every API surface shown in the new README snippets against the actual source (HasCount, Contains(predicate), .And chaining, Because, [GenerateAssertion], T.Mock() (C# 14 extension static members), Arg.Any<T>() (auto-imported via global using static), Mock.HttpClient/OnGet/RespondWithJson, Mock.Logger<T>/VerifyLog().AtLevel().ContainingMessage(), TestWebApplicationFactory<T>, AspireFixture<T>, PageTest, [FsCheckProperty]) — all exist and match the shown usage. Also traced the benchmark script's field access (latest.categories[...], Mean/Version/NA handling) against the real docs/static/benchmarks/latest.json produced in this PR — matches, including the NA → — fallback for the missing TUnit_AOT SetupTeardownTests cell.

Finding:

README.md — "Assertions that explain themselves" section:

await Assert.That(order.Items)
    .HasCount(3)
    .And.Contains(item => item.Sku == "ABC-123");

CollectionAssertionBase.HasCount(int, ...) is marked [Obsolete("Use Count().IsEqualTo(expectedCount) instead.")] (TUnit.Assertions/Sources/CollectionAssertionBase.cs:332). This compiles (it's a warning, not an error), but the flagship README — the first thing new users read — is showcasing a deprecated API as the idiomatic way to assert on collection size. Since the whole point of this section is "here's the current best way to write assertions," recommend swapping to .Count().IsEqualTo(3).And.Contains(...) so the example doesn't steer newcomers toward something the library itself is trying to move away from.

Everything else — the benchmark automation script, the workflow wiring (git add ... README.md so the auto-PR now includes README changes), and the rest of the README content — looks correct and well cross-checked.

HasCount(int) is [Obsolete]; showcase the recommended Count().IsEqualTo(3) path instead. Chains identically via CollectionCountEqualsAssertion.

'a fraction of a second slower' understates source-gen cost on very large suites (scales with test count). Reworded to 'pay a little up front'.

Property injection lets subclasses inherit shared fixtures without re-threading constructor parameters; note constructor injection still works.

claude · 2026-07-16T12:14:23Z

Code review (follow-up)

Re-reviewed after the four fixup commits. Diff scope: README.md, .github/scripts/update-readme-benchmarks.js (new), .github/workflows/speed-comparison.yml.

Previously flagged issue — resolved: the HasCount(3) obsolete-API example was swapped for .Count().IsEqualTo(3) in e56c5a5. Confirmed the current diff no longer references the obsolete overload. The two other fixup commits (softened build-time claim, property-injection framing) are accurate reflections of the code and don't introduce new issues.

New finding — maintainability (minor, non-blocking):

update-readme-benchmarks.js hardcodes its own SCENARIOS map (AsyncTests, DataDrivenTests, MatrixTests, ScaleTests, MassiveParallelTests, SetupTeardownTests → display labels), duplicating the category key list that already exists as RUNTIME_DESCRIPTIONS in the sibling process-benchmarks.js (.github/scripts/process-benchmarks.js:12-19). The two maps have diverged failure semantics: process-benchmarks.js falls back to a generated description for an unrecognized category (RUNTIME_DESCRIPTIONS[testClass] || \Performance benchmark for ${testClass}.`), while the new script's .filter(([key]) => latest.categories[key])` silently drops any category not in its hardcoded map — so if a new benchmark scenario is ever added to the runtime suite, it shows up on the docs benchmarks page but silently never appears in the README table, with no CI failure to catch the omission.

Since this table is now stitched into the weekly automated PR with zero human review expected (per the PR description), a silent-drop failure mode is the one place this automation could quietly go stale. Two options that would close the gap:

Have update-readme-benchmarks.js warn/console.error (and optionally fail) when latest.json contains a category key with no entry in SCENARIOS, rather than passing over it silently.
Or derive the scenario list from latest.json's own category keys plus a single shared label map imported by both scripts, so there's one source of truth instead of two that can drift.

Not a blocker for this PR — the automation as written matches today's six scenarios correctly — but worth a quick follow-up so the "never goes stale" guarantee in the PR description actually holds for future scenario additions.

Everything else — the marker-replacement logic, the workflow step ordering (runs after process-benchmarks.js, before the git add that now includes README.md), and the rest of the README content/snippets — checks out.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6e4ed6d0c3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-16T12:15:56Z

+### ASP.NET Core
+
+```csharp
+public class ApiFactory : TestWebApplicationFactory<Program>;


Use valid class declarations in integration snippets

Readers copying the new ASP.NET Core sample hit a C# syntax error here because public class ...; is not a valid class declaration; the Aspire sample below uses the same semicolon-only form. These examples need an empty body such as { } (or another valid declaration) before users can try the TUnit integration code.

Useful? React with 👍 / 👎.

Updated [TUnit](https://github.com/thomhurst/TUnit) from 1.59.0 to 1.61.15. <details> <summary>Release notes</summary> _Sourced from [TUnit's releases](https://github.com/thomhurst/TUnit/releases)._ ## 1.61.15  ## What's Changed ### Other Changes * feat: Allow disabling the automatic html report upload to upload-artifacts@v7 by @Crashdummyy in thomhurst/TUnit#6447 * fix: stop retrying artifact upload on non-retryable status codes by @thomhurst in thomhurst/TUnit#6449 ### Dependencies * chore(deps): update tunit to 1.61.0 by @thomhurst in thomhurst/TUnit#6437 * chore(deps): update verify to 31.24.3 by @thomhurst in thomhurst/TUnit#6438 * chore(deps): update dependency opentelemetry.instrumentation.aspnetcore to 1.17.0 by @thomhurst in thomhurst/TUnit#6440 * chore(deps): update verify to 31.25.0 by @thomhurst in thomhurst/TUnit#6442 * chore(deps): update dependency docusaurus-plugin-llms to ^0.5.0 by @thomhurst in thomhurst/TUnit#6443 * chore(deps): update opentelemetry to 1.17.0 by @thomhurst in thomhurst/TUnit#6441 ## New Contributors * @Crashdummyy made their first contribution in thomhurst/TUnit#6447 **Full Changelog**: thomhurst/TUnit@v1.61.0...v1.61.15 ## 1.61.0  ## What's Changed ### Other Changes * docs: revamp README with feature showcase and auto-updating benchmarks by @thomhurst in thomhurst/TUnit#6430 * docs: align docs homepage messaging with revamped README by @thomhurst in thomhurst/TUnit#6431 * fix(engine): emit ECMA-335 metadata-format type names in TestMethodIdentifierProperty by @thomhurst in thomhurst/TUnit#6433 * fix(benchmarks): make SetupTeardownTests JSON tests Native AOT compatible by @thomhurst in thomhurst/TUnit#6434 * Organize repository into conventional .NET layout by @thomhurst in thomhurst/TUnit#6435 ### Dependencies * chore(deps): update dependency polyfill to v11 by @thomhurst in thomhurst/TUnit#6418 * chore(deps): update dependency tunit.aspire to 1.6* by @thomhurst in thomhurst/TUnit#6419 * chore(deps): update tunit to 1.6* by @thomhurst in thomhurst/TUnit#6420 * chore(deps): update dependency polyfill to 11.0.1 by @thomhurst in thomhurst/TUnit#6421 * chore(deps): update dependency polyfill to 11.0.1 by @thomhurst in thomhurst/TUnit#6422 * chore(deps): update verify to 31.24.2 by @thomhurst in thomhurst/TUnit#6424 * chore(deps): update microsoft.build to 18.8.2 by @thomhurst in thomhurst/TUnit#6426 * chore(deps): update dependency microsoft.net.stringtools to 18.8.2 by @thomhurst in thomhurst/TUnit#6425 * chore(deps): update actions/setup-dotnet action to v6 by @thomhurst in thomhurst/TUnit#6427 * chore(deps): bump websocket-driver from 0.7.4 to 0.7.5 in /docs by @dependabot[bot] in thomhurst/TUnit#6429 * chore(deps): update opentelemetry to 1.17.0 by @thomhurst in thomhurst/TUnit#6432 **Full Changelog**: thomhurst/TUnit@v1.60.0...v1.61.0 ## 1.60.0  ## What's Changed ### Other Changes * feat: cross-process test report aggregation — merged HTML report + single GitHub summary by @thomhurst in thomhurst/TUnit#6415 ### Dependencies * chore(deps): update tunit to 1.59.0 by @thomhurst in thomhurst/TUnit#6398 * chore(deps): update verify to 31.24.1 by @thomhurst in thomhurst/TUnit#6399 * chore(deps): update microsoft.testing to 2.3.2 by @thomhurst in thomhurst/TUnit#6401 * chore(deps): update mstest to 4.3.2 by @thomhurst in thomhurst/TUnit#6402 * chore(deps): update actions/setup-node action to v7 by @thomhurst in thomhurst/TUnit#6403 * chore(deps): update dependency microsoft.net.test.sdk to 18.8.0 by @thomhurst in thomhurst/TUnit#6404 * chore(deps): update dependency microsoft.net.test.sdk to 18.8.1 by @thomhurst in thomhurst/TUnit#6405 * chore(deps): update dependency fsharp.core to 10.1.302 by @thomhurst in thomhurst/TUnit#6406 * chore(deps): update dependency microsoft.templateengine.authoring.cli to v10.0.302 by @thomhurst in thomhurst/TUnit#6407 * chore(deps): update dependency microsoft.entityframeworkcore to 10.0.10 by @thomhurst in thomhurst/TUnit#6410 * chore(deps): update dependency dotnet-sdk to v10.0.302 by @thomhurst in thomhurst/TUnit#6409 * chore(deps): update dependency system.commandline to 2.0.10 by @thomhurst in thomhurst/TUnit#6412 * chore(deps): update dependency microsoft.templateengine.authoring.templateverifier to 10.0.302 by @thomhurst in thomhurst/TUnit#6411 * chore(deps): update microsoft.aspnetcore to 10.0.10 by @thomhurst in thomhurst/TUnit#6413 * chore(deps): update microsoft.extensions to 10.0.10 by @thomhurst in thomhurst/TUnit#6414 * chore(deps): update microsoft.extensions to 10.8.0 by @thomhurst in thomhurst/TUnit#6416 * chore(deps): update dependency polyfill to v11 by @thomhurst in thomhurst/TUnit#6417 **Full Changelog**: thomhurst/TUnit@v1.59.0...v1.60.0 Commits viewable in [compare view](thomhurst/TUnit@v1.59.0...v1.61.15). </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=TUnit&package-manager=nuget&previous-version=1.59.0&new-version=1.61.15)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Updated [TUnit.Core](https://github.com/thomhurst/TUnit) from 1.59.0 to 1.61.15. <details> <summary>Release notes</summary> _Sourced from [TUnit.Core's releases](https://github.com/thomhurst/TUnit/releases)._ ## 1.61.15  ## What's Changed ### Other Changes * feat: Allow disabling the automatic html report upload to upload-artifacts@v7 by @Crashdummyy in thomhurst/TUnit#6447 * fix: stop retrying artifact upload on non-retryable status codes by @thomhurst in thomhurst/TUnit#6449 ### Dependencies * chore(deps): update tunit to 1.61.0 by @thomhurst in thomhurst/TUnit#6437 * chore(deps): update verify to 31.24.3 by @thomhurst in thomhurst/TUnit#6438 * chore(deps): update dependency opentelemetry.instrumentation.aspnetcore to 1.17.0 by @thomhurst in thomhurst/TUnit#6440 * chore(deps): update verify to 31.25.0 by @thomhurst in thomhurst/TUnit#6442 * chore(deps): update dependency docusaurus-plugin-llms to ^0.5.0 by @thomhurst in thomhurst/TUnit#6443 * chore(deps): update opentelemetry to 1.17.0 by @thomhurst in thomhurst/TUnit#6441 ## New Contributors * @Crashdummyy made their first contribution in thomhurst/TUnit#6447 **Full Changelog**: thomhurst/TUnit@v1.61.0...v1.61.15 ## 1.61.0  ## What's Changed ### Other Changes * docs: revamp README with feature showcase and auto-updating benchmarks by @thomhurst in thomhurst/TUnit#6430 * docs: align docs homepage messaging with revamped README by @thomhurst in thomhurst/TUnit#6431 * fix(engine): emit ECMA-335 metadata-format type names in TestMethodIdentifierProperty by @thomhurst in thomhurst/TUnit#6433 * fix(benchmarks): make SetupTeardownTests JSON tests Native AOT compatible by @thomhurst in thomhurst/TUnit#6434 * Organize repository into conventional .NET layout by @thomhurst in thomhurst/TUnit#6435 ### Dependencies * chore(deps): update dependency polyfill to v11 by @thomhurst in thomhurst/TUnit#6418 * chore(deps): update dependency tunit.aspire to 1.6* by @thomhurst in thomhurst/TUnit#6419 * chore(deps): update tunit to 1.6* by @thomhurst in thomhurst/TUnit#6420 * chore(deps): update dependency polyfill to 11.0.1 by @thomhurst in thomhurst/TUnit#6421 * chore(deps): update dependency polyfill to 11.0.1 by @thomhurst in thomhurst/TUnit#6422 * chore(deps): update verify to 31.24.2 by @thomhurst in thomhurst/TUnit#6424 * chore(deps): update microsoft.build to 18.8.2 by @thomhurst in thomhurst/TUnit#6426 * chore(deps): update dependency microsoft.net.stringtools to 18.8.2 by @thomhurst in thomhurst/TUnit#6425 * chore(deps): update actions/setup-dotnet action to v6 by @thomhurst in thomhurst/TUnit#6427 * chore(deps): bump websocket-driver from 0.7.4 to 0.7.5 in /docs by @dependabot[bot] in thomhurst/TUnit#6429 * chore(deps): update opentelemetry to 1.17.0 by @thomhurst in thomhurst/TUnit#6432 **Full Changelog**: thomhurst/TUnit@v1.60.0...v1.61.0 ## 1.60.0  ## What's Changed ### Other Changes * feat: cross-process test report aggregation — merged HTML report + single GitHub summary by @thomhurst in thomhurst/TUnit#6415 ### Dependencies * chore(deps): update tunit to 1.59.0 by @thomhurst in thomhurst/TUnit#6398 * chore(deps): update verify to 31.24.1 by @thomhurst in thomhurst/TUnit#6399 * chore(deps): update microsoft.testing to 2.3.2 by @thomhurst in thomhurst/TUnit#6401 * chore(deps): update mstest to 4.3.2 by @thomhurst in thomhurst/TUnit#6402 * chore(deps): update actions/setup-node action to v7 by @thomhurst in thomhurst/TUnit#6403 * chore(deps): update dependency microsoft.net.test.sdk to 18.8.0 by @thomhurst in thomhurst/TUnit#6404 * chore(deps): update dependency microsoft.net.test.sdk to 18.8.1 by @thomhurst in thomhurst/TUnit#6405 * chore(deps): update dependency fsharp.core to 10.1.302 by @thomhurst in thomhurst/TUnit#6406 * chore(deps): update dependency microsoft.templateengine.authoring.cli to v10.0.302 by @thomhurst in thomhurst/TUnit#6407 * chore(deps): update dependency microsoft.entityframeworkcore to 10.0.10 by @thomhurst in thomhurst/TUnit#6410 * chore(deps): update dependency dotnet-sdk to v10.0.302 by @thomhurst in thomhurst/TUnit#6409 * chore(deps): update dependency system.commandline to 2.0.10 by @thomhurst in thomhurst/TUnit#6412 * chore(deps): update dependency microsoft.templateengine.authoring.templateverifier to 10.0.302 by @thomhurst in thomhurst/TUnit#6411 * chore(deps): update microsoft.aspnetcore to 10.0.10 by @thomhurst in thomhurst/TUnit#6413 * chore(deps): update microsoft.extensions to 10.0.10 by @thomhurst in thomhurst/TUnit#6414 * chore(deps): update microsoft.extensions to 10.8.0 by @thomhurst in thomhurst/TUnit#6416 * chore(deps): update dependency polyfill to v11 by @thomhurst in thomhurst/TUnit#6417 **Full Changelog**: thomhurst/TUnit@v1.59.0...v1.60.0 Commits viewable in [compare view](thomhurst/TUnit@v1.59.0...v1.61.15). </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=TUnit.Core&package-manager=nuget&previous-version=1.59.0&new-version=1.61.15)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

thomhurst temporarily deployed to Pull Requests July 16, 2026 10:55 — with GitHub Actions Inactive

docs: use non-obsolete Count().IsEqualTo in README assertion example

e56c5a5

HasCount(int) is [Obsolete]; showcase the recommended Count().IsEqualTo(3) path instead. Chains identically via CollectionCountEqualsAssertion.

thomhurst had a problem deploying to Pull Requests July 16, 2026 12:04 — with GitHub Actions Error

docs: soften build-time claim in README performance section

6605d48

'a fraction of a second slower' understates source-gen cost on very large suites (scales with test count). Reworded to 'pay a little up front'.

thomhurst had a problem deploying to Pull Requests July 16, 2026 12:09 — with GitHub Actions Error

docs: lead DI example with property injection

6e4ed6d

Property injection lets subclasses inherit shared fixtures without re-threading constructor parameters; note constructor injection still works.

thomhurst merged commit 9b4317a into main Jul 16, 2026
3 of 4 checks passed

thomhurst deleted the docs/readme-revamp branch July 16, 2026 12:12

thomhurst temporarily deployed to Pull Requests July 16, 2026 12:12 — with GitHub Actions Inactive

chatgpt-codex-connector Bot reviewed Jul 16, 2026

View reviewed changes

thomhurst mentioned this pull request Jul 16, 2026

docs: align docs homepage messaging with revamped README #6431

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

docs: revamp README with feature showcase and auto-updating benchmarks#6430

docs: revamp README with feature showcase and auto-updating benchmarks#6430
thomhurst merged 4 commits into
mainfrom
docs/readme-revamp

thomhurst commented Jul 16, 2026

Uh oh!

codacy-production Bot commented Jul 16, 2026

Uh oh!

claude Bot commented Jul 16, 2026

Uh oh!

Uh oh!

claude Bot commented Jul 16, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Jul 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

thomhurst commented Jul 16, 2026

Summary

README changes

Benchmark automation

Verification

Uh oh!

codacy-production Bot commented Jul 16, 2026

Not up to standards ⛔

Uh oh!

claude Bot commented Jul 16, 2026

Code review

Uh oh!

Uh oh!

claude Bot commented Jul 16, 2026

Code review (follow-up)

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jul 16, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant