- Use
make importsbefore committing any change to Go code. - Use
go mod tidyafter any change to ago.mod. - Run
make lintand fix all reported issues before submitting a pull request. - Run the e2e tests before submitting a pull request.
- When possible, try to keep pull requests small and self-contained to make reviews easier. Follow
the repository's
.github/pull_request_template.mdand make sure to focus more on the reasons, background and encountered problems that motivated the change and less on reiterating code changes.
- Lines in Markdown files should not exceed 100 characters (use explicit line breaks).
- Use
make clean build test-e2efor running e2e tests. - To run a specific test package, use the
WHATenvironment variable, likeWHAT=./test/e2e/apiexport make test-e2e, or theTEST_FLAGSvariable likeTEST_FLAGS="-v -run NameOfTheTestFunction" make test-e2e.
- When generating a changelog for a new release, group all relevant pull requests based on their
kind/...label. Output these groups in descending order of importance. - Only include pull requests in the changelog that have a
release-noteblock in their descriptions on GitHub that is not empty orNONE. - List each pull request in the following form:
#<number>: <release note> (by @<author>)