. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in indentation. ∗ Use 2 spaces in everything except Go. ∗ In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more sentences or which implications it has (e.g. other parts in the system have to be adapted.) Sometimes this message can also contain more material for reference e.g. benchmark numbers to justify why the change was

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adhere to the Go coding guidelines and watch out for these common errors. * Contain a description message that is as detailed as possible. Here is a great example https://github.com/vitessio/vitess/pull/6543 inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more sentences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed as possible. Here is a great example https://github.com/vitessio/vitess/pull/6543 inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more sentences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed as possible. Here is a great example https://github.com/vitessio/vitess/pull/6543 inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more sentences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed as possible. Here is a great example https://github.com/vitessio/vitess/pull/6543 inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more sentences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adhere to the Go coding guidelines and watch out for these common errors. • Contain a description message that is as detailed as possible. Here is a great example https://github.com/vitessio/vitess/ pull/6543 inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: 40 – – : This is a short description of the change. If necessary , more sentences

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in indentation. ∗ Use 2 spaces in everything except Go. ∗ In Go, just use goimports. • Commit message format: 22 – : This is a short description of the change. If necessary , more sentences or which implications it has (e.g. other parts in the system have to be adapted.) Sometimes this message can also contain more material for reference e.g. benchmark numbers to justify why the change was

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Creating a message table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in indentation. ∗ Use 2 spaces in everything except Go. ∗ In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more sentences or which implications it has (e.g. other parts in the system have to be adapted.) Sometimes this message can also contain more material for reference e.g. benchmark numbers to justify why the change was