Web Development Reading List #123: Meaningful Git Commits and HTTP Status Codes


This week I mostly spent time on fixing bugs, improving a deployment workflow and on getting another new front-end project structured. One major takeaway from this was that it’s good to have a proper deployment workflow in place already in the early stages of a project.
To document appropriately in git what has been done in a commit instead of sleazily writing “changed [XY] because of [some arbitrary reason]”. By doing so, it becomes easier for myself, or someone else, to identify bugs at a later stage.
The post Web Development Reading List #123: Meaningful Git Commits and HTTP Status Codes appeared first on Smashing Magazine.
From our sponsors: Web Development Reading List #123: Meaningful Git Commits and HTTP Status Codes