copilotkit-contribute

To set up the CopilotKit monorepo for local development, you must fork the repository, clone it locally, and use pnpm to install dependencies and build packages before creating a branch.

The best way to submit a pull request to the CopilotKit project is to develop your feature, run tests and linting, and ensure your commits follow the conventional commit format before submitting.

Yes, you need Git for repository management and pnpm for dependency management to contribute to CopilotKit, as the workflow requires these tools for forking, cloning, and building the monorepo.

The conventional commit format for CopilotKit contributions ensures your commit messages follow a standardized structure, which is enforced during the committing phase before you submit your pull request.

Yes, you can use this workflow to manage dependencies in a pnpm monorepo because it provides specific instructions for installing dependencies and building packages within the CopilotKit project structure.

Your CopilotKit contribution workflow requires building packages before testing to ensure all local dependencies in the monorepo are correctly compiled and available for the test suite to execute.