We use GitHub to host code, build code, create releases, track issues and feature requests, and accept pull requests.
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
We use GitHub issues to raise any bug or request new features. GitHub will present templates for both.
Pull requests are the best way to propose changes to the codebase (we use GitHub Flow). We actively welcome your pull requests:
- Fork this repo and create a branch from master.
- If you've added code that should be tested, add tests.
- If you've changed the config, update the README.md file.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
When there are code changes from myself or from a pull request, a tag will be created following semantic versioning. This will trigger the CI to generate all the artifacts for commit.
This project uses Go modules to manage dependencies on external packages
To add or update a new dependency, use the go get
command:
# Pick the latest tagged release.
go get example.com/some/module/pkg
# Pick a specific version.
go get example.com/some/module/pkg@vX.Y.Z
You have to commit the changes to go.mod
and go.sum
before submitting the pull request.