Gitflow is dead? What are the alternatives?

Question

git

In a small team (startup) we use github. Thinking about organizing team work with git. In every post from habr on this topic, git flow is praised. I read about it and it sounds great. For the convenience of working with this technique, many advise using the nvie/gitflow extensions . Yes, only the last commit there was in 2012, and the issue list is not at all happy. By the way, all found articles are also quite old.
Questions arise:
How should the team work with git in 2015 (methodologies, tools)?
Is there an actively developed fork of nvie/gitflow or alternatives?

Answer 1

I have not been talking to git for a very long time, but I have the impression that git flow is not in extensions, but in the heads.
I believe it is possible to single out the role of the guardian of the git flow traditions in the team. If it will be very difficult, you can automate routine scripts on your own.
Although, I confess, I'm not very competent here. I'm still working with git solo "without an ensemble".

Answer 2

Chesslovo bro, you are a programmer! If you are not satisfied with the existing "bicycles" - build your own! When introducing Git in our company, we immediately agreed that we would use gitflow as a methodology for working with Git. I had to straighten it a little for myself, but still. And I don’t really understand what kind of routine operations we are talking about, because everything is done simply from my favorite IDE (release branches, merge, delete branches). The main thing is to follow the rules, then there is less chance of shooting yourself in the foot.

Answer 3

As Dmitry Makarov correctly noted , "git flow is not in extensions, but in the heads." Git flow requires understanding, responsibility and discipline from all project participants.

Answer 4

I use gitflow on many projects, everything suits me.