Skip to content
Go to file
Cannot retrieve contributors at this time
42 lines (28 sloc) 2.54 KB


OpenBazaar is an open source project. We love contributions! This document outlines some contribution guidelines so that your contributions can be included in the codebase.


Issues should be used primarily for bug reports and directly actionable features. It's OK if you open an issue to ask a question or to start a discussion, however don't take offense if the issue is closed after a few days. General discussion of the protocol is probably better fleshed out in slack.

Go Guidelines

You must run gofmt before each commit. Travis will fail if you do not run it. Most IDEs have the ability to set gofmt to run on save or at specified times.

All commits are checked with golangci-lint using the .golangci.yml config in the repo.

Additionally, we like to keep the Go Report Card score at A or better. So keep those other tests in mind when you commit.


If you add new code, please submit a unit test with it. We might not accept the PR without it. Additionally, you are expected to make the appropriate changes to existing tests if they are affected by your commits. This also includes the integration tests in the qa package.

Pull Requests

If your PR isn't ready to merge make sure you specify this somehow. For example by placing [WIP] in the PR title. Ideally you should include a task list in the PR message to track the progress of the PR.

The PR must be approved by more than one member of the team with write access prior to merging.


To keep things consistent comment fragments should start with a capital letter and end with no period. If the comment is one or more full sentences (a sentence has at least a subject and a verb) then the sentences should end with a period.


Please keep all of your commits atomic.

Also, be sure to follow the seven rules of a great git commit message.

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how

Finally, please sign your commits.