Codeship Golang Best Practices
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
To achieve consistency and simplicity throughout our Go codebases. This is to aid in readability, maintainability and efficiency when onboarding and during code review.
This document is built upon and inspired by a number of articles and talks given over the past few years by the Go community. These practices are not unique, everything is borrowed.
We run markdown-spellcheck in CI on all contributions. Failure to amend such errors will result in changes being rejected.
make spellcheckto get quick validation
make fix-spellingto use
mdspellinteractive correction functionality and to maintain the
see output and see mdspell for details on how to maintain the
Everyone interacting in the project and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the Code of Conduct.