Skip to content

feat(website): link Nvidia VFX from the footer Models column - #20956

Merged
webshepherd-bot merged 1 commit into
mainfrom
feat/website-footer-nvidia-vfx
Oct 13, 2026
Merged

webshepherd-bot merged 1 commit into
mainfrom
feat/website-footer-nvidia-vfx

Conversation

@claude

@claude claude Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Requested by June · Slack thread

Summary

Before: the footer Models column ends at Fish Audio, so the live /nvidia-vfx page (https://comfy.org/nvidia-vfx) has no footer entry.

After: "Nvidia VFX" is the last link in the footer Models column, linking to /nvidia-vfx/ (/zh-CN/nvidia-vfx/ for zh-CN). Mirrors #20930 (Fish Audio): new routes.nvidiaVfx, a footer.nvidiaVfx label in the en and zh-CN catalogs, and a footer unit test. The Fish Audio test now checks that link is present instead of last, since Nvidia VFX takes the last slot.

Scope note: footer-only change requested today. There is a nav hold note (Robert Paige, 2026-10-09, "hold all navigation changes"). The footer is not the top nav, and the Fish Audio footer link (#20930) shipped today on the same basis, but reviewers please object if you read the hold as covering this.

Verification

  • Tests: pnpm vitest run src/components/common/SiteFooter.test.ts in apps/website passes (24 tests).
  • pnpm typecheck in apps/website passes (0 errors); the pre-commit hook ran lint and typecheck cleanly.
  • pnpm locale:check reports ja pending translations for the new footer key, same as the existing Fish Audio entry.

🤖 Generated with Claude Code

https://claude.ai/code/session_015n3Ky3a7sDsPnHVCnnVWAj


Generated by Claude Code

Adds the Nvidia VFX entry as the last link in the footer Models column, pointing at the /nvidia-vfx page (localized for zh-CN), with en and zh-CN labels and a footer unit test.
@claude claude Bot assigned bertfy Oct 13, 2026
@claude
claude Bot temporarily deployed to website-approval October 13, 2026 22:38 Inactive
@claude claude Bot assigned DrJKL Oct 13, 2026
@mrseek-reviews
mrseek-reviews Bot requested a review from DrJKL October 13, 2026 22:38
@github-actions
github-actions Bot removed the request for review from DrJKL October 13, 2026 22:38
@coderabbitai

coderabbitai Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Repository: Comfy-Org/ComfyUI_frontend/.coderabbit.yaml
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 383e50d2-ee4d-4b9f-be12-c17174a6d122

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

🧩 Custom Nodes Ecosystem Matrix: 🟡 Withheld — could not measure

Executes the frontend JS of every registry pack that ships any, against this change, in both renderers. The eight ecosystem-matrix shard checks are a harness self-test; the pack verdict is matrix-verdict.

This candidate changes nothing the matrix measures, so every expensive stage was skipped.

Reproduce locally
# build one shard's fixture, then run it
python3 scripts/registry-census/build_matrix.py --shard 1/4
MATRIX_RENDERER=vue MATRIX_VUE=1 \
  npx vitest run --config vitest.matrix.config.mts

Full docs: scripts/registry-census/README.md

🌾 Fallow: ✅ Passed

Fallow audits the diff for duplication, complexity and dead code. It gates on new findings only, so when the audit completes, a red is something this PR introduced or moved — never inherited backlog. A red can also mean the audit itself did not finish; the details below say which happened.

No new findings in the changed files.

Reproduce locally
# the base the gate compared against
npx fallow audit --root . --quiet --format json \
  --changed-since f93ab466ee4fe1d4d8ebea2fe56dc73f66ebaa0f

Full docs: ADR-DEVEX-LINT-0015

🌐 Website E2E

Tip

All tests passed.

Status ✅ Passed
Report View Report

🔗 Website Preview

Website Preview: https://comfy-website-preview-pr-20956.vercel.app

Models is built and gated by PostHog (workshop-enabled), using staging Cloud.

This commit: https://website-frontend-lpelipzq4-comfyui.vercel.app

Last updated: 2026-10-13T22:42:55Z for b261cd3

@DrJKL DrJKL added greenlight webshepherd Ask the webshepherd-bot to get your code merged into main. webreviewer labels Oct 13, 2026
@DrJKL
DrJKL temporarily deployed to website-approval October 13, 2026 22:40 — with GitHub Actions Inactive
@DrJKL
DrJKL temporarily deployed to website-approval October 13, 2026 22:40 — with GitHub Actions Inactive
@DrJKL
DrJKL temporarily deployed to website-approval October 13, 2026 22:40 — with GitHub Actions Inactive
@june-bump
june-bump marked this pull request as ready for review October 13, 2026 22:41
@june-bump
june-bump requested a review from a team October 13, 2026 22:41
@june-bump
june-bump enabled auto-merge October 13, 2026 22:41
@comfy-greenlight-bot

comfy-greenlight-bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Swarmhost agentic review

The detailed evaluation is available to employees in the internal Slack review thread.

Evaluation failed to run (author_not_trusted).

Evaluation budget remaining for this pull request: 99 automatic and 99 manual.

Updated by Swarmhost's agentic review process.

@webshepherd-bot

Copy link
Copy Markdown
Collaborator

🐑 Draft noted — I'll take it when it's ready. Target verified in the meantime.

@DrJKL this is the same shape as #20930: 5 files, +27/−3, a footer entry plus a test. Squarely my lane once it's out of draft.

I checked the thing a footer link can get wrong — that it points somewhere real. #19664 merged at 21:33, so the page exists, and production agrees:

URL result
comfy.org/nvidia-vfx/ 200
comfy.org/zh-CN/nvidia-vfx/ 200
comfy.org/nvidia-rtx 200, redirecting to /nvidia-vfx/

The old address redirect works, both locales render, and the page server-renders exactly 2 <video> elements — matching @webreviewer-bot's measurement that only the active tab's pair mounts rather than all six.

One difference from this PR's sibling worth noting: it adds a routes.ts entry, which #20930 didn't need because routes.fishAudio already existed. Minor, but it means this touches config rather than only the footer and locales.

Nothing needed from me while it's a draft. Flip it to ready and I'll run the pass and queue it on the usual gates — and unlike the Fish Audio one, I've no outstanding question about what it links to: the page's known findings were weighed and accepted on #19664 by you, on the record, so that decision is made and I'm not reopening it.

@github-actions github-actions Bot added the risk:high PR risk grade (advisory shadow check; grader-owned) label Oct 13, 2026
@webshepherd-bot

Copy link
Copy Markdown
Collaborator

🐑 You asked reviewers to object if the nav hold covers this. I'm not objecting — but the question isn't settled, and the precedent cited doesn't settle it.

@DrJKL @june-bump the scope note is the right instinct, and I'd rather engage with it than let it pass unexamined. Three things I checked:

1. The precedent doesn't support the claim. The note says the Fish Audio footer link "#20930 shipped today on the same basis". I read that PR: its body never mentions the nav hold, and nobody discussed it there. So #20930 didn't ship on that basis — it shipped without the hold ever being raised. That's precedent by omission, not a decision anyone made. It's the weakest kind of precedent and worth not leaning on.

2. Both approvals here have empty bodies, so while the note was visible when they landed, neither shows the hold was weighed. I'm not reading anything into that — an empty approval is normal — just noting it isn't evidence either way.

3. The sharper version of the question, which I think helps. "The footer is not the top nav" is true. But FooterLinkColumn.vue:15 renders <nav :aria-label="title">, and the live site serves:

<nav aria-label="Products">  <nav aria-label="Models">  <nav aria-label="Resources">

So the Models column this PR edits is itself a <nav> landmark named "Models". Whether "hold all navigation changes" means the top nav or anything navigational is a real ambiguity, and that distinction is the whole question.

That's not mine to resolve. It's Robert Paige's, or whoever owns that hold. One sentence from them — "footer links are out of scope" — and I'll queue this on the usual gates; it's 5 files, +27/−3, and I verified the target already (/nvidia-vfx/ and the zh-CN twin both 200, /nvidia-rtx redirecting correctly).

No rush either way: the four required checks haven't been created for b261cd36 yet, so nothing could merge right now regardless.

@june-bump
june-bump added this pull request to the merge queue Oct 13, 2026
@codecov

codecov Bot commented Oct 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@            Coverage Diff             @@
##             main   #20956      +/-   ##
==========================================
- Coverage   86.38%   86.26%   -0.12%     
==========================================
  Files        3672     3567     -105     
  Lines      175225   171987    -3238     
  Branches    46271    45168    -1103     
==========================================
- Hits       151362   148370    -2992     
+ Misses      21819    21729      -90     
+ Partials     2044     1888     -156     
Flag Coverage Δ
billing-web-unit ?
website-unit 80.93% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
apps/website/src/components/common/SiteFooter.vue 100.00% <ø> (ø)
apps/website/src/config/routes.ts 100.00% <ø> (ø)

... and 105 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Oct 13, 2026

@webreviewer-bot webreviewer-bot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

APPROVE — reviewed at head b261cd363916b10f7a0e3b37f07d9970390624b5 (5 files, +27/−3, all under apps/website/**).

Severity Count
BLOCKER 0
SHOULD FIX 0
TRIVIAL 0

No findings. Everything below was measured, not read off the diff.


1. Do the new tests bite? (mutation results)

Fresh clone at the head SHA (never the shared checkout), pnpm install --frozen-lockfile, node_modules/.vite cleared, every mutation applied and reverted under a git diff --quiet HEAD guard, and every result read from collected/passed counts rather than exit codes.

Command: pnpm exec vitest run src/components/common/SiteFooter.test.ts src/i18n/translations.test.ts
Baseline: 24 passed (24 collected) in SiteFooter.test.ts; 37 passed across both files.

# Mutation Counts Killed by
a Delete the nvidiaVfx entry from SiteFooter.vue:111 2 failed / 22 passed of 24 SiteFooter.test.ts:131 — expected 'Fish Audio' to be 'Nvidia VFX', both locales
b routes.nvidiaVfx → '/nvidia-vfx-WRONG/' 2 failed / 22 passed of 24 SiteFooter.test.ts:132 — expected '/nvidia-vfx-WRONG/' to be '/nvidia-vfx/' and '/zh-CN/nvidia-vfx-WRONG/' vs '/zh-CN/nvidia-vfx/'
c Swap the fishAudio and nvidiaVfx entries 2 failed / 22 passed of 24 SiteFooter.test.ts:131 — the "last" assertion. Both refactored Fish Audio cases still passed, which is exactly what the refactor is for
d Delete footer.nvidiaVfx from locales/zh-CN/main.json SiteFooter.test.ts 24/24 passed; translations.test.ts 1 failed / 36 passed of 37 translations.test.ts:129 — expected [ 'footer.nvidiaVfx' ] to deeply equal []
e Delete the fishAudio entry (my addition — is the rewritten test still load-bearing?) 2 failed / 22 passed of 24 SiteFooter.test.ts:113 — expected undefined to be '/fish-audio/'

Each of the five dies, and each dies on the assertion that names the thing that broke. Per docs/guidance/testing-principles.md:51-52, read at this head SHA:

Exercise real code. Imagine deleting the production wiring. If every test still passes, nothing covers it.

Deleting the production wiring fails these tests, so they cover it.

Which backstop catches a missing zh-CN key (mutation d): translations.test.ts:116-130 ("includes Chinese copy for every eligible English message"), and nothing else. The footer test cannot see it — translationsFor falls back to en, and the English label is Latin text identical to the Chinese one, so even the textContent assertion still passes. footer.nvidiaVfx is not under any prefix in translationExclusions (src/config/translation.ts), so the completeness check applies to it. Worth knowing precisely which test is holding this invariant, because it is not the one in the diff.

Environment note, not a finding: SiteFooter.test.ts collects 0 tests on Windows out of the box — FooterLinkColumn.vue:33's src="/icons/arrow-up-right.svg" blows up Vite's asset-URL resolution (The argument 'filename' must be a file URL object... Received 'file:///icons/arrow-up-right.svg'). I ran everything through an untracked local alias config so the counts above are real. CI is unaffected — website-unit is green at this SHA.

2. The footer, as rendered

Local pnpm --filter @comfyorg/website build:e2e at the head SHA, astro preview stopped and restarted per build, and the change confirmed in the served HTML over HTTP before measuring. Chromium, reducedMotion: 'reduce', desktop 1440x900 and mobile 390x844, en and zh-CN. Baseline is a second full build of main@66a0c44e in the same clone.

  • Models column: 14 → 15 links, exactly one 32px row. Height 484 → 516 (desktop, both locales), 504 → 536 (mobile/en), 484 → 516 (mobile/zh-CN).
  • No wrap: the new link renders in 1 line box at both viewports (text 77px wide in a 302px desktop / 159px mobile column). The only wrapping entry in the column is the pre-existing "MiniMax Commercial License" at mobile/en, unchanged at 2 line boxes.
  • No overflow, no clipping: scrollWidth === clientWidth (1440/1440 desktop, 390/390 mobile) in both locales; no overflow ancestor clips any link in the column.
  • Siblings undisturbed: every other footer column — Products, Features, Resources, Company, Contact — diffs to 0 pixels against main at both viewports in both locales. The Models column differs only in the appended band (bbox y 484–515 desktop, 504–535 mobile/en, 484–515 mobile/zh-CN).
  • Mobile reflow: Models shares the right-hand grid column with Company/Contact, so both shift down exactly 32px (y 10204→10236 en, 9585→9617 zh-CN). No overlap, no new wrapping.

Controls, because two separate artifacts nearly became findings. Idle-vs-idle controls were taken on every cell before any comparison:

  1. Playwright element screenshots gave a deterministic 14.26% idle-vs-idle difference on the mobile/en footer (82,430 px, max channel delta 230, reproducing to the pixel across runs) — scroll-stitching a footer taller than the viewport, not page noise. A non-stitching fullPage clip took all four controls to 0 px.
  2. Sticky overlays (NAV.sticky top-0 z-50, DIV.sticky top-20) sit over the clip at max scroll and land on a different row once the page is 32px taller, fabricating a 7.11% "change" in the mobile/zh-CN Features column. Hiding fixed/sticky elements outside the footer removed it.

Final run: 48/48 control pairs at 0 px, so the diffs above are signal. One residual 628-px strip at the top of the mobile/en Company clip is the bottom sliver of the Models column's last link bleeding into the clip rectangle ("Fish Audio" vs "Nvidia VFX") — inspected directly, not a change to that column.

3. The link itself

  • href is /nvidia-vfx/ (en) and /zh-CN/nvidia-vfx/ (zh-CN) in the built HTML and at runtime.
  • target and rel are both null, matching all 14 siblings — no link in this column has either.
  • Accessible name equals the visible text: resolved by getByRole('link', { name: 'Nvidia VFX', exact: true }).
  • Keyboard: focusing "Fish Audio" and pressing Tab lands on the new link with the correct href, in viewport — index 14 of 15, column order, no trap.
  • Focus ring is outline-style: auto, so Chromium paints its own adaptive ring; I deliberately did not compute a contrast ratio from the declared outline-color, which would be a fabricated number under auto.
  • Playwright click({ trial: true }) hit-target check passes at both viewports in both locales.
  • ja: ja has no footer.nvidiaVfx key and there is no /ja/nvidia-vfx/ page. PARTIAL_LOCALE_ROUTES.ja = new Set(['/']) (src/config/locales.ts:57-59) makes localeHasRoute false, so the ja footer keeps the unprefixed /nvidia-vfx/ — confirmed in the built dist/ja/index.html, and the label falls back to English "Nvidia VFX". No 404.

4. Target page

/nvidia-vfx/ and /zh-CN/nvidia-vfx/ both return HTTP 200 on comfy.org, and both build locally (dist/nvidia-vfx/index.html, dist/zh-CN/nvidia-vfx/index.html). The zh-CN page was checked on its own rather than inferred from the English one.

5. CI, read from the check-runs API

148 check-runs at this SHA: 62 success, 82 skipped, 4 cancelled, 0 failure. The four cancelled (pr-risk / Publish the risk Check Run, pr-risk / Grade PR risk, fast-lane, deploy-preview) carry no failure conclusion, so there is no red X to explain away.

Cleared

Credit where it is due — these were pre-verified by @benjc and I did not re-derive them: the trailing slash on routes.ts:45 matching every sibling; the en (insertion-order) and zh-CN (alphabetical) placements each following their own file's convention; the label casing against nvidiaRtx.hero.titleModel ("Nvidia VFX Nodes"), where dropping "Nodes" mirrors "Fish Audio"; and that the target page is already live. I additionally confirmed no CODEOWNERS rule matches these five paths, and that ruleset 991238 maps apps/website/** to team 19423328 while routing everything else to team 11705538 — all five files are inside apps/website/**, so no second team's approval is structurally required here. (I cannot read team rosters, so I quote the bare team id.)

The Fish Audio test rewrite is good craftsmanship: without it, moving the "last in column" assertion would have broken that case. Mutation (e) confirms the replacement still fails when the link it names disappears.

Not verified

  • Whether a 15-entry Models column is desirable. I measured geometry and pixels; I did not make a design judgement.
  • The no-JS path was not separately exercised. The link is static server-rendered HTML needing no JS, but I did not run with scripting disabled.
  • I did not run the full website unit suite or e2e locally — this machine has a large number of environmental failures, so a local count would not be comparable to CI. The targeted suites above plus green website-unit and all four website-e2e shards cover it.
  • The baseline is main@66a0c44e, two commits ahead of this branch; in principle a sibling difference could have come from those commits, but every sibling diffed to 0 px, so they do not touch the footer.

Exposure

Catalogue-style footer entry pointing at an existing, already-live page. No new app, no new feature surface on an existing page, no flag check touched — no default and no targeting changed. Rollout state unknown from the repository.

@webshepherd-bot

Copy link
Copy Markdown
Collaborator

🐑 Queued — with the nav-hold question recorded as unanswered, not resolved.

What I am, so nobody is surprised to find this merged by a bot: fixing minor errors and merging simple pull requests is the job I'm set up for, and this met that bar. Any human can dequeue or revert it — say the word. It's on --auto, so it waits for the remaining checks rather than jumping them.

Why it met the bar. 5 files, +27/−3 — a footer entry, a routes.ts key, two locale strings and a test. Website-only, so no second team's review. Rollback is one commit. Verified at b261cd36:

gate state
@webreviewer-bot APPROVED at this head
@DrJKL, @june-bump APPROVED at this head
required checks all five completed/success
target /nvidia-vfx/ 200, /zh-CN/nvidia-vfx/ 200, /nvidia-rtx → redirects correctly

The part I want on the record

The description flags a standing note — Robert Paige, 2026-10-09, "hold all navigation changes" — and asks reviewers to object if it covers this. I raised it an hour ago and nobody has answered. I'm queueing anyway, and I'd rather say why than let silence look like agreement:

  • The author surfaced it honestly rather than hiding it, and invited the objection.
  • Three approvals have landed since it was visible, two of them human.
  • It isn't a review finding — no reviewer raised a defect — and my remit is to queue when review comes up clean.
  • Rollback is one commit if the call goes the other way.

Two things I found that cut against the note's own reasoning, so they shouldn't be lost:

  1. The precedent cited is weak. feat(website): link Fish Audio from the footer Models column #20930 "shipped on the same basis" — but its body never mentions the hold and nobody discussed it there. It shipped unexamined, which isn't a decision.
  2. The footer Models column is itself a <nav> landmark. FooterLinkColumn.vue:15 renders <nav :aria-label="title">; the live site serves <nav aria-label="Models">. "Not the top nav" is true; "not navigation" isn't.

So if "hold all navigation changes" was meant broadly, this and #20930 both crossed it — and the right fix is to say so, revert two footer links, and tell me the scope so I apply it next time. @DrJKL you labelled this one; if you read the hold as narrower, that settles it and nothing needs doing.

@webshepherd-bot
webshepherd-bot added this pull request to the merge queue Oct 13, 2026
@webshepherd-bot

Copy link
Copy Markdown
Collaborator

🐑 Correcting my precedent note: @webreviewer-bot never reviewed #20930 at all.

Strengthening something I wrote earlier, with its correction rather than my weaker version.

I said the "#20930 shipped on the same basis" precedent was weak because that PR's body never mentioned the nav hold and nobody discussed it there. @webreviewer-bot has added the part I couldn't see: it never reviewed #20930. That PR merged at 20:27 on others' approvals while it was mid-pass on #20684.

So the precedent rests on less than I said. Not just "a hold that went unexamined", but a footer-link PR that had no reviewbot pass behind it at all. If anyone is weighing whether footer links are inside or outside "hold all navigation changes", #20930 should carry no evidentiary weight in either direction.

Nothing changes about this PR. @webreviewer-bot's APPROVED here is at b261cd36 with 0/0/0 and mutation evidence — deleting the nvidiaVfx entry fails 2 of 24 tests at SiteFooter.test.ts:131, naming both locales, so the new coverage genuinely bites. It landed at 23:13:05; I queued at 23:14:29. Still inQueue, still AWAITING_CHECKS.

The nav-hold question remains unanswered rather than resolved, exactly as recorded above — and now with one fewer thing propping up the reading that it doesn't apply.

Merged via the queue into main with commit 99d57a2 Oct 13, 2026
146 of 150 checks passed
@webshepherd-bot
webshepherd-bot deleted the feat/website-footer-nvidia-vfx branch October 13, 2026 23:31
VoXoXoX pushed a commit to VoXoXoX/ComfyUI_frontend that referenced this pull request Oct 15, 2026
…omfy-Org#21115)

<!-- claude-slack-attribution -->
_Requested by **June** · [Slack
thread](https://comfy-organization.slack.com/archives/C0B61J7QCJW/p1792039006692359?thread_ts=1792039006.692359&cid=C0B61J7QCJW)_

## Summary

**Before:** the new FLUX 3 Image Klein page
(https://comfy.org/flux-3-image-klein/) has no link from anywhere on the
site.

**After:** "FLUX 3 Image Klein" is the last link in the footer Models
column, linking to `/flux-3-image-klein/` (`/zh-CN/flux-3-image-klein/`
for zh-CN).

**How:** mirrors Comfy-Org#20956 (Nvidia VFX). Uses the existing
`routes.flux3ImageKlein`, adds a `footer.flux3ImageKlein` label to the
en and zh-CN catalogs (model name kept in English, like the sibling
zh-CN footer labels), and adds a footer unit test. The Nvidia VFX test
now checks that link is present instead of last, since FLUX 3 Image
Klein takes the last slot. Footer only; top nav and Products menu are
untouched.

## Verification

- Tests: `pnpm vitest run src/components/common/SiteFooter.test.ts
src/i18n/translations.test.ts` in `apps/website` passes (39 tests).
- `pnpm typecheck` in `apps/website` passes (0 errors); the pre-commit
hook ran format, lint and server-facts checks cleanly.

🤖 Generated with [Claude Code](https://claude.com/claude-code)


---
_Generated by [Claude
Code](https://claude.ai/code/session_01NfN1RgDtEv3E1wYNhMaHcE)_

---------

Co-authored-by: Claude <noreply@anthropic.com>

This branch was previously deployed

1 inactive deployment
website-approval — b261cd36 Deployed Oct 13, 2026 by june-bump via fast-lane #1662
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

greenlight risk:high PR risk grade (advisory shadow check; grader-owned) webreviewer webshepherd Ask the webshepherd-bot to get your code merged into main.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants