In the end I’ve decided I don’t like the tool or the model, though both are interesting.
I think this is because I’m used to working in fairly large teams where we may have some people working on one release and others working on the next, in this situation I want release branches that are fairly long lived, and to create topic branches from them.
In fact in one project we dropped the master branch altogether and just used a series or release barnches, always merging the older release branches into the newer (further from launch) ones.
The other main reason is that gitflow hides some of the mechanics of git in a way that seems to me to hinder peoples understanding of what they are doing, it’s a shame it down’t output the git commands it uses - that would allow people to use it to get started then move on later if they want.
The commands also seem very slow to me which is odd when you are used to git being fast.
Documentation on gitflow seems sparse, with some commands incomplete (git flow support * , gitflow feature checkout)
The best I could find is the source, and particularly the "summary" bits
The project wiki does have some addiutional info on command line options