Docs?

[Brian Kotek]

Hi folks, maybe I'm missing something but looking at Github and
searching Google doesn't turn up much in the way of documentation for
gitflow. I've found a handful of basic screencasts and blog entries
but nothing that looks official or really comprehensive. I mean, there
are a bunch of commands (publish, track, pull, diff, rebase, etc.)
that I can't find anything at all about. What are these? How are they
different from the standard git commands? When would I use them vs.
the standard commands (and should I use them at all)? Even across the
various blog posts, the workflow they show and the commands they use
vary, so I'm not even sure what is technically the correct (intended)
way to use gitflow.

Gitflow looks very interesting and as a contributor to open source
projects I know that docs can often get the short end of the stick.
But from what I can see there's just *nothing* in this area *at all*.
I'm not asking for a vast set of docs (though that would be nice), but
at this point practically anything would be a good start. Even if it
were just a couple of wiki pages.

Thanks,

Brian

[pro-...@optusnet.com.au]

I'm actually trying to work this out myself. So far the only way I found out to see what the extra parameters do is to look at the script code.

[Mark Derricutt]

One of these days I should re-record my screencast with a bit more thought behind it, I did that first one off-the-cuff and whilst its ok, it could be better.

But you're right - beyond the basic docs on the github site there isn't really much more in the way of documentation which should probably be done.

I'm sure Vincent will appreciate a pull request with wiki docs :)  And if there's nothing by the time I get back from holiday I might look into pulling something together myself...


--
"Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree