Skip to content

docs: refresh contributing guide#3645

Closed
Osraka wants to merge 1 commit into
ComposioHQ:nextfrom
Osraka:docs/update-contributing-guide-3487
Closed

docs: refresh contributing guide#3645
Osraka wants to merge 1 commit into
ComposioHQ:nextfrom
Osraka:docs/update-contributing-guide-3487

Conversation

@Osraka

@Osraka Osraka commented Jun 24, 2026

Copy link
Copy Markdown

Summary

  • refresh CONTRIBUTING.md around the current monorepo layout (ts/, python/, docs/, and .github/)
  • document the mise.toml / mise.lock toolchain flow instead of generic Node/Bun/Python prerequisites
  • add focused TypeScript, Python, docs, E2E, provider/example, changeset, and PR workflow guidance
  • remove stale guidance for top-level packages/, legacy version files, mandatory boilerplate file headers, and manual release steps from the main contributor guide

Fixes #3487.

Why

The existing guide still described an older repository structure and setup flow, which can send new contributors toward stale paths or obsolete commands. This keeps the root contributor guide as a practical orientation document and points release-specific details to the dedicated TypeScript and Python release docs.

Validation

  • git diff --check HEAD~1..HEAD

Not run:

  • pnpm exec prettier --check CONTRIBUTING.mdpnpm is not available in this local shell. This is a docs-only change, and the diff whitespace check is clean.

@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

Osraka is attempting to deploy a commit to the Composio Team on Vercel.

A member of the Team first needs to authorize it.

@jkomyno

Copy link
Copy Markdown
Collaborator

Hi, thank you, but I think this is deprecated by #3651, which is merged already

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.

docs: update outdated CONTRIBUTING.md for current repo structure

2 participants