copilotkit-contribute

To set up the CopilotKit monorepo locally, you need to fork and clone the repository, then bootstrap the environment using pnpm and Nx to manage dependencies and build tasks across the V1 and V2 packages.

CopilotKit pull requests must pass mandatory linting, formatting, and testing checks. Adhering to conventional commit standards and using the correct branch naming conventions ensures your PR meets the CI pipeline requirements for successful integration.

You build and test packages in the CopilotKit monorepo by utilizing Nx and pnpm to execute targeted build, lint, and test commands across the specific V1 and V2 workspaces affected by your changes.

Yes, pnpm and Nx are required to contribute to CopilotKit. They manage the monorepo's dependencies and orchestrate the build, test, and linting tasks necessary to validate your code before submitting a pull request.

The standard workflow involves forking the repository, creating a feature branch with the correct naming convention, executing build and test commands via Nx and pnpm, and submitting a PR passing all CI validation steps.

Your CopilotKit contribution fails the CI pipeline if it does not pass mandatory linting, formatting, and testing requirements, or if it violates conventional commit standards and branch naming protocols enforced by the monorepo.