Formatting standardizes how source code looks and feels, giving a growing team a shared style instead of leaving every developer to make separate choices. A style guide can settle details such as tabs versus spaces, bracket placement, and spacing between functions. section 1.3.4 section 5.3
The practical goal is to remove formatting from everyday decision-making. Go provides a built-in formatter that can move brackets, replace spaces with tabs, and consolidate spacing; comparable tools include Prettier for JavaScript and autopep8 for Python. section 5.3
Make formatting part of the delivery workflow:
- Choose a shared style and the formatter that applies it. section 5.3
- Run the check in CI before tests so inconsistent code is rejected early. section 5.8
A formatting gate
A Makefile can define check-format as test -z $$(go fmt ./...), causing the command to pass only when formatting produces no changes. A CI format-check job can run that target before the test job, keeping style problems out of later delivery stages.
