The Ultimate Commit Token
I’ve rarely had to use a commit token. The teams I’ve worked in generally edit unrelated source items as much as is possible. Over the years I’ve read about various amusing items being used as commit tokens: rubber ducks, action figures, hats and little flags, to name a few. The general idea is that you should physically have the token to be allowed to commit – meaning there are no updates made to the source repository so your changes will go in cleanly.
It is possible that this could be side-stepped though – Mr Naughty Committer might pretend to be holding the Pokémon and commit – how can the source repository be expected to know where Pikachu is at any given moment??
However, one of my colleagues had a great idea the other day – ‘The Ultimate Commit Token”. Simply appropriate one of those single use password setups with a single key fob. You could try borrowing it from your corporate VPN setup – I’m sure they wouldn’t miss it.
Wire your pre-commit script into the server-side element and have the fob floating between developers. Et Voila! One very annoying, yet extremely effective commit token!!!
I know, I know, it’s not very exotic looking, but fear not! I reckon it would look natty glued to the back of Spud Of Nine.
No related posts.