I put a git commit hash into each project build automatically, it looks like this:
0ba74ab23528b122923e83b5a7c6d2ce2e5a9313
It can hardly be easily read and remembered by a developer.
I have an option to use a short version of the commit hash that looks like this:
0ba74ab
Which looks better but there is still room to make it more readable and easy to memorize.
I think about generating a human-readable name for the hash which could be remembered and more or less stably mapped to a unique hash.
It could look like a string generated from a set of predefined strings with some suffix, like this:
drunk-coala-83
empty-pockets-95
Or just a synthetic vocable word like this:
jimakrow
As the project is not large and used only by me and a couple of my teammates, I can easily integrate it.
Is this technique used somewhere in projects? How can I tackle this problem so that to keep git workflow unaltered. Where should I start with this problem?
You can use git tag to name your commits.
Remember that you have to explicitly push the tags with git push origin tag_name, otherwise they just exist on your local.