. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OOT)'`; do kill -9 $process done; export VTDATAROOT=/tmp/vtdataroot ./101_initial_cluster.sh Coding Standards Backwards Compatibility Vitess is being used to power many mission-critical production request should meet the following requirements: • Use the Pull Request Template • Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OOT)'`; do kill -9 $process done; export VTDATAROOT=/tmp/vtdataroot ./101_initial_cluster.sh Coding Standards Backwards Compatibility Vitess is being used to power many mission-critical production the master branch. Every pull request should meet the following requirements: * Adhere to the Go coding guidelines and watch out for these common errors. * Contain a description message that is as detailed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . '`; do kill -9 $process done; export VTDATAROOT=/tmp/vtdataroot ./101_initial_cluster.sh 34 Coding Standards Backwards Compatibility Vitess is being used to power many mission-critical production request should meet the following requirements: • Use the Pull Request Template • Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . '`; do kill -9 $process done; export VTDATAROOT=/tmp/vtdataroot ./101_initial_cluster.sh 36 Coding Standards Backwards Compatibility Vitess is being used to power many mission-critical production request should meet the following requirements: • Use the Pull Request Template • Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Coding Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . '`; do kill -9 $process done; export VTDATAROOT=/tmp/vtdataroot ./101_initial_cluster.sh 35 Coding Standards Backwards Compatibility Vitess is being used to power many mission-critical production request should meet the following requirements: • Use the Pull Request Template • Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed

bad shape, not because of bad transient state or bad user queries) • Does this change match our coding conventions / style? Linter was run and is happy? • Does this match our current patterns? Example

bad shape, not because of bad transient state or bad user queries) • Does this change match our coding conventions / style? Linter was run and is happy? • Does this match our current patterns? Example

bad shape, not because of bad transient state or bad user queries) • Does this change match our coding conventions / style? Linter was run and is happy? • Does this match our current patterns? Example