Home - Tags - Bookmarks - About

Commit to Revision Control with Care

Tuesday, 01 January 2013

We should always commit to revision control with care.

Often, developers provide commit messages that are incomplete, lowercase, with orthographic permutations. Even worse, snapshots can contain code that doesn’t even compile.

In a signed document the rules and regulations can be altered and then another document is going to be created and signed, but the original document will always remain signed.

As signatures in documents can't be erased so do recorded snapshots, at least it is not always an easy task.

After a snapshot has been recorded it acts like a signature for the developer – should we ever put our signature roughly?

━━━

This post has been filed under #misc

Feedback

Have feedback on this page? Let @nikosbaxevanis know on twitter. Need help or found a bug? Contact me.


© 2011-2018 Nikos Baxevanis. All written content on this site is provided under a Creative Commons ShareAlike license. All code is provided under a MIT license unless otherwise stated.