For all contributors, we recommend the standard GitHub flow based on forking and pull requests.
For significant changes, please create an issue to let everyone know what you're planning to work on, and to track progress and design decisions.
Please read vitess.io/contributing/ where we provide more information:
- How to make yourself familiar with Go and Vitess.
- How to go through the GitHub workflow.
- What to look for during code reviews.
At this time, we will not be accepting contributions that only fix spelling, naming or grammatical errors in documentation, code, comments or elsewhere, from accounts created in the last 365 days. We appreciate your interest in contributing to Vitess, and we encourage you to contribute in other ways.