Skip to content

docs: move standup bot example code to its own repo#3768

Open
Sarah Simionescu (sarahsimionescu) wants to merge 1 commit into
nextfrom
sarah/unpublish-standup-example
Open

docs: move standup bot example code to its own repo#3768
Sarah Simionescu (sarahsimionescu) wants to merge 1 commit into
nextfrom
sarah/unpublish-standup-example

Conversation

@sarahsimionescu

Copy link
Copy Markdown
Collaborator

The daily standup bot example now lives in its own standalone repo: ComposioHQ/standup-slackbot.

What this does

  • Removes the deployable copy under docs/examples/standup-slackbot/ (the full runnable project).
  • Removes the RepoBrowser full-source snapshot (docs/lib/standup-bot-source.json) and deregisters the standup source in repo-browser.tsx.
  • Rewrites the example page's "The whole project" section to link to the new repo instead of embedding the source.

What stays

  • The entire tutorial page: prose, images, mermaid, and all inline <FileBuildup> teaching snippets (backed by standup-bot-build.ts, untouched).
  • The shared RepoBrowser and FileBuildup components, still used by the other example pages.

⚠️ Merge blockers

  1. ComposioHQ/standup-slackbot is currently internal — the docs link will 404 for external readers until an org admin flips it to public. Do not merge until then.
  2. Let CI validate the docs build.

🤖 Generated with Claude Code

The daily standup bot now lives in its own standalone repo,
ComposioHQ/standup-slackbot. Remove the deployable copy under
docs/examples/standup-slackbot and the RepoBrowser full-source snapshot
(standup-bot-source.json), and point the example page's "The whole project"
section at the repo instead.

The tutorial itself is unchanged: prose, images, mermaid, and the inline
FileBuildup teaching snippets all stay. Only the full deployable source moves out.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 8, 2026 12:01am

Request Review

@claude

claude Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Claude finished Sarah Simionescu (@sarahsimionescu)'s task in 55s —— View job


Docs Review — Looks good ✅

Reviewed against docs-reviewer.md. This is a clean extraction of the runnable project into its own repo, and the docs stay self-consistent.

  • Read docs-reviewer.md review criteria
  • Review changes to standup-slackbot.mdx
  • Review repo-browser.tsx component change
  • Check for dangling references to deleted files / standup source
  • Post review verdict

What I verified:

Check Result
No dangling RepoBrowser source="standup" usages ✅ None remain — the only user was this page, now replaced with a <Cards> link
No leftover imports of standup-bot-source.json ✅ Removed cleanly from repo-browser.tsx; no other importers
Other RepoBrowser sources still wired slack-bot and local-workbench sources + registrations untouched
Teaching snippets still backed docs/lib/standup-bot-build.ts is intact and all 6 <FileBuildup> blocks still resolve
Config filename consistency ✅ Both the <Card> description and the "Run it" step now reference standup.config.example.tsstandup.config.ts consistently
Index/gallery entry ✅ Page still carries its gallery frontmatter; no meta.json entry needed

Component change (repo-browser.tsx): Just deregisters the standup source — no accessibility/mobile/pattern concerns, and the remaining sources are handled identically.

One non-blocking note (already tracked by you): the Card links to https://github.com/ComposioHQ/standup-slackbot, which will 404 for external readers until the repo is flipped to public. You've already flagged this as a merge blocker in the PR description — just re-confirming it's the one thing gating merge from a reader's perspective. Nothing to change in the code.

A developer following this page would land on a working external repo (once public) and the inline tutorial remains fully intact. Ship it once the repo is public and CI is green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant