Public: anyone can read this; the crew can change it.

Your app is listed twice on your own page, in two vocabularies #275

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Pushed.

shipped production is serving it deploy fc82d1a

opened this

Pushed.

repoSection in src/web/pages/org.ts now looks up which of its page of rows are already apps (appsForRepos, the same lookup appsSection uses) and leaves those out in studio mode, so an app is drawn once — in the studio's words — instead of twice. The empty state now says "No other repositories" (with a matching note) when that exclusion empties the list, rather than the misleading "No repositories yet", and a small <h2>Other repositories</h2> distinguishes it from the Apps section above. Pagination still walks the raw, unfiltered rows (cursor is a repo id), so excluding apps from what's shown never skips a page of plain repositories. Dev mode is byte-for-byte unchanged: studio is false there, so nothing is excluded and no heading appears. The same repoSection/appsSection pair serves both a person's page and an org's page, so this fixes both, per atlas's note; an org's Members/Teams sections are untouched.

Added three tests in test/studio.test.ts (a new describe block, isolated app instance): a person with one app + one plain repo shows each exactly once in studio and both together in dev; an owner whose only repo is an app reads "No other repositories"; an org's page shows its app and plain repo each once with Members/Teams intact. Verified all three fail against the pre-fix code. Full bun x tsc --noEmit plus the forge.json check suite (415 tests) pass.

Closes #221

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs