Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replace git-flow with git-flow-avh and adjust instructions accordingly #54

Merged
merged 1 commit into from
Apr 21, 2016

Conversation

ChristianUlbrich
Copy link
Contributor

The initial toolset of git-flow at https://github.com/nvie/gitflow is not developed any further (i.e. dead). The last commit is 4 years old.
There are several big issues with the old git-flow tool, the most daunting (i.e. git describedoes not work):

The old git-flow does also not support git-flow-specific hooks:

The git-flow AVH Edition from https://github.com/petervanderdoes/gitflow-avh seems to be the commonly agreed on successor to git-flow and is a fork of the original git-flow that addresses these problems. It is backward-compatible with the original git-flow and addresses the above problems.

Therefore I changed the installation instructions and changed them to install git-flow-avh. I have used the instructions from: https://github.com/petervanderdoes/gitflow-avh/wiki/Installation for the individual platforms. However as I am on OS X, I have only tested OS X (ports + brew). The instructions for Linux mention, that on a current Ubuntu apt-get install git-flow will install the AVH edition of git-flow anyway. That's why I did not change the Linux installation instructions.

Your cheat-sheet is nice and we use it at work for new developers and maybe you consider making the switch to git-flow-avh as well.

link to avh wiki instead of abandoned nvie wiki deep link to Windows instructions
@danielkummer danielkummer merged commit 114c38f into danielkummer:gh-pages Apr 21, 2016
@ChristianUlbrich
Copy link
Contributor Author

Cheers! Thanks for merging!

On a side note, the fixes for being git-describe friendly do slightly modify the branching work-flow and I have not yet had a deeper look at it - so you might need to update your branching pictures as well. Maybe I can have a look at it as well, but don't count on it - I am also buried in work. :)

@danielkummer
Copy link
Owner

Thanks for the side-note, this is planned during the whole "rework" of the cheatsheet, I also plan to extend it with new feature and possibly a few project workflow examples..

But regarding work - I think most of us are in the same boat in that regard ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants