docs: move standup bot example code to its own repo#3768
docs: move standup bot example code to its own repo#3768Sarah Simionescu (sarahsimionescu) wants to merge 1 commit into
Conversation
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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Claude finished Sarah Simionescu (@sarahsimionescu)'s task in 55s —— View job Docs Review — Looks good ✅Reviewed against
What I verified:
Component change ( One non-blocking note (already tracked by you): the 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. |
The daily standup bot example now lives in its own standalone repo: ComposioHQ/standup-slackbot.
What this does
docs/examples/standup-slackbot/(the full runnable project).RepoBrowserfull-source snapshot (docs/lib/standup-bot-source.json) and deregisters thestandupsource inrepo-browser.tsx.What stays
<FileBuildup>teaching snippets (backed bystandup-bot-build.ts, untouched).RepoBrowserandFileBuildupcomponents, still used by the other example pages.ComposioHQ/standup-slackbotis currentlyinternal— the docs link will 404 for external readers until an org admin flips it to public. Do not merge until then.🤖 Generated with Claude Code