pull request must go through a code review and get approved before it will be merged into the master branch. What to look for in a Review Both authors and reviewers need to answer these general questions: com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local master branch, do this: $ git checkout master (master) $ git pull upstream master Note: In the example output the fact that the command must be run from the branch master. You can omit the upstream master from the git pull command when you let your master branch always track the main vitessio/vitess repository

pull request must go through a code review and get approved before it will be merged into the master branch. What to look for in a Review Both authors and reviewers need to answer these general questions: com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local master branch, do this: $ git checkout master (master) $ git pull upstream master Note: In the example output the fact that the command must be run from the branch master. You can omit the upstream master from the git pull command when you let your master branch always track the main vitessio/vitess repository

pull request must go through a code review and get approved before it will be merged into the master branch. What to look for in a Review Both authors and reviewers need to answer these general questions: com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local master branch, do this: $ git checkout master (master) $ git pull upstream master Note: In the example output the fact that the command must be run from the branch master. 25 You can omit the upstream master from the git pull command when you let your master branch always track the main vitessio/vitess repository

mission-critical production workloads at very large scale. Moreover, many users deploy directly from the master branch. It is very important the changes made by contributors do not break any existing workloads. In order pull request must go through a code review and get approved before it will be merged into the master branch. Every pull request should meet the following requirements: * Adhere to the Go coding guidelines com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local master branch, do this: $ git checkout master (master) $ git pull upstream master Note: In the example output

mission-critical production workloads at very large scale. Moreover, many users deploy directly from the master branch. It is very important the changes made by contributors do not break any existing workloads. In order pull request must go through a code review and get approved before it will be merged into the master branch. Every pull request should meet the following requirements: • Use the Pull Request Template • Adhere com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local master branch, do this: $ git checkout master (master) $ git pull upstream master Note: In the example output

mission-critical production workloads at very large scale. Moreover, many users deploy directly from the main branch. It is very important the changes made by contributors do not break any existing workloads. In order pull request must go through a code review and get approved before it will be merged into the main branch. Every pull request should meet the following requirements: • Use the Pull Request Template • Adhere com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local main branch, do this: $ git checkout main (main) $ git pull upstream main Note: In the example output above

mission-critical production workloads at very large scale. Moreover, many users deploy directly from the master branch. It is very important the changes made by contributors do not break any existing workloads. In order pull request must go through a code review and get approved before it will be merged into the master branch. Every pull request should meet the following requirements: • Use the Pull Request Template • Adhere com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local master branch, do this: $ git checkout master (master) $ git pull upstream master Note: In the example output

mission-critical production workloads at very large scale. Moreover, many users deploy directly from the main branch. It is very important the changes made by contributors do not break any existing workloads. In order pull request must go through a code review and get approved before it will be merged into the main branch. Every pull request should meet the following requirements: • Use the Pull Request Template • Adhere com:vitessio/vitess.git (fetch) upstream git@github.com:vitessio/vitess.git (push) Now to sync your local main branch, do this: $ git checkout main (main) $ git pull upstream main Note: In the example output above

main repository at https://github.com/vitessio/vitess was used as the codebase to be verified. ▪ branch master commit 092479406b27ae61a8fcd146a0e08af2d51a7245 ◦ Furthermore, the minimal reference client client https://github.com/vitessio/messages was used as additional illustration of use-cases. ▪ branch master commit 7d2ac2189573a7d26cf0f42e17df749673e3d16f ◦ The testers received unencumbered access to

The Vitess maintainers will fix issues upstream, and OSS-Fuzz will pull the latest Vitess master branch the next time it performs a fuzz run and verify that a given issue has been fixed. Vitess's fuzzers