Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
23 lines (16 loc) · 1.21 KB

CONTRIBUTING.md

File metadata and controls

23 lines (16 loc) · 1.21 KB

Contributing to KurrentDB MCP Server

Working with the Git

We use master as the main development branch. We do our best to ensure a clean history. To do so, commits are automatically squashed into a single logical commit when pull requests are merged.

To contribute to KurrentDB:

  1. Fork the repository.
  2. Create a feature branch from the master (or release) branch.
  3. It's recommended that feature branches use a rebase strategy (see more in Git documentation). We also highly recommend using clear commit messages that represent the unit of change.
  4. Rebase the latest source branch from the main repository before sending PR.
  5. When ready to create the Pull Request on GitHub check to see what has previously changed.

Licensing and legal rights

By contributing to KurrentDB MCP Server:

  1. You assert that contribution is your original work
  2. You assert that you have the right to assign the copyright for the work
  3. You accept the Contributor License Agreement (CLA) for your contribution
  4. You accept the License