Skip to content

Rewrite CONTRIBUTING.md around BenchBot Discord workflow - #13

Merged
bingran-you merged 1 commit into
mainfrom
docs/benchbot-contributing
Jul 1, 2026
Merged

Rewrite CONTRIBUTING.md around BenchBot Discord workflow#13
bingran-you merged 1 commit into
mainfrom
docs/benchbot-contributing

Conversation

@bingran-you

Copy link
Copy Markdown
Contributor

What changed

Rewrites CONTRIBUTING.md so the recommended way to contribute new environments is chatting with BenchBot in the BenchFlow Discord (https://discord.gg/G9dg3EfSva), interacting with it the way you would drive Claude Code or Codex:

  1. Join the Discord
  2. Connect your own agent credentials via /bot-connect + the dashboard connect page (never paste keys in Discord)
  3. @BenchBot with the environment you want to build (example prompt included)
  4. Provide API docs, sample payloads, and files in the thread
  5. Iterate — replies continue the session, each round posts a live preview URL
  6. Follow sessions/runs/traces/artifacts on the dashboard (benchchat.vercel.app)
  7. Maintainer review lands the finished environment in packages/environments/

Also kept, condensed under a direct-PR section: contribution areas table, boundaries (now framed as applying to both paths), dev setup, validation matrix, and the PR checklist. Added a footer linking Discord, the code of conduct, and the security policy.

Why

Contributing an environment previously required full local setup and PR mechanics. BenchBot makes the primary path conversational and setup-free.

Validation

Docs-only change. Verified all relative links point at existing files, and that benchchat.vercel.app is live (benchchat.benchflow.ai DNS still unresolved, so the doc uses the vercel.app domain).

Make BenchBot in the BenchFlow Discord the recommended path for
contributing new environments: join, connect credentials, describe the
environment, share reference docs, iterate in-thread, follow the build
on the dashboard. Keep boundaries and a condensed direct-PR path
(dev setup, validation matrix, checklist) for direct code changes.
@bingran-you
bingran-you merged commit b88e997 into main Jul 1, 2026
7 checks passed
@bingran-you
bingran-you deleted the docs/benchbot-contributing branch July 1, 2026 21:31
bingran-you added a commit that referenced this pull request Jul 1, 2026
Make BenchBot in the BenchFlow Discord the recommended path for
contributing new environments: join, connect credentials, describe the
environment, share reference docs, iterate in-thread, follow the build
on the dashboard. Keep boundaries and a condensed direct-PR path
(dev setup, validation matrix, checklist) for direct code changes.
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