Git book

This might be a good thing to study.

Autocommitting under git

Since I use Github to serve my site, a git autocommit has to be part of my publishing process.  Here are ways to do that, at StackExchange.

Git is really a lot more opaque than it needs to be

Here's a fantastic tutorial about Git branching that has finally made a lot of things make sense to me.  But seriously, the management commands provided, while they make perfect sense in terms of the actual things git is doing, make no sense whatsoever in terms of the semantics of managing branches and versions.

I conclude that git's actual UI is horrible.  Moreover, there's no real reason for there to be multiple DVCSs anyway, since they all essentially do the same thing - implement the same abstract architecture.  Again, the specifics of the UI obscure the actual things being done and why they're done.

A version history as represented in git (or any other DVCS) should be a part of the documentation in graphical form, like any other part of the documentation.  That report should then be available as a contextual orientation for performing actions on the official history of the project.  Specific branches and commits should be tracked explicitly and graphically - obviously while preserving the underlying command structure for those that think that way, but seriously.  Git is crazy.

How to use git again

More and more I think a workflow tool for daily use is just about essential.  Some curated git tips and workflows.