We really appreciate contributions, but they must meet the following requirements:
- A PR should have a brief description of the problem/feature being proposed
- Pull requests should target the
development
branch - Existing tests should pass and any new code should be covered with it's own test(s) (use travis-ci)
- New functions should be documented clearly
- Code should pass
golint
,go vet
andgo fmt
We merge PRs into development
, which is then tested in a sharded, replicated environment in our datacenter for regressions. Once everyone is happy, we merge to master - this is to maintain a bit of quality control past the usual PR process.
Thanks for helping!