Page Comparison

...

Since CockroachDB is open source, most of the instructions for hacking on CockroachDB live in this repo, cockroachdb/cockroach. You should start by reading the top level of this section of the wiki. 

Then, look at our Go style guidecoding guidelines and the Google Go Code Review guide it links to. These are linked to from the other pages in this wiki, but they're easy to miss. If you haven't written any Go before CockroachDB, you may want to hold off on reviewing the style guide until you've written your first few functions in go.

...

Fix your style violations

First, read the Go style guidecoding guidelines again, looking for any style violations. It's easier to remember a style rule once you've violated it.

...

•  Developing
  •  Create a GitHub fork of cockroachdb/cockroach
  •  Read through the contributor guide in this wiki
•  Submitting your first PR
  •  Push to a feature branch on your personal fork
  •  Verify you've followed the Go style guidecoding guidelines
  •  Verify you've read What is a Good CockroachDB PR
  •  Verify you've read Submitting your contribution
  •  Ensure files you've added, if any, have a license block
  •  Run make check
  •  Split your change into logical commits with good messages
•  Addressing feedback
  •  Amend the appropriate commits and force-push
  •  Respond to all feedback with "Done" or a counterargument
•  Merging
  •  Comment bors r=reviewer to ask Craig to merge