Development Standards
These standards apply to code contributions across the Epinio repositories.
Pull requests
Pull requests for a code change should reference the issue they're for. This enables issues to serve as a central point of reference for a change. For example, if a pull request fixes or completes an issue, the commit or pull request should include something like:
Closes #123
This indicates that the PR closes issue #123 when merged.
Semantic versioning
Epinio follows semantic versioning.
This doesn't cover other tools included in Epinio. Kubernetes has its own release versioning scheme that's similar to SemVer but semantically different.
Coding style
Epinio expects Go code formatted with go fmt.
Epinio further follows the style guidelines at: