Issues with git-flow

By popularity By time

Martin Wolf recommended Issues with git-flow from scottchacon.com:

There are a number of advantages to deploying so regularly. If you deploy every few hours, it’s almost impossible to introduce large numbers of big bugs. Little issues can be introduced, but then they can be fixed and redeployed very quickly.

Estimated reading time: 11 min

Martin Wolf The GitHub Flow.

August 22, 2012 | 0

Rouven Rieker recommended Issues with git-flow from scottchacon.com:

Git itself is fairly complex to understand, making the workflow that you use with it more complex than necessary is simply adding more mental overhead to everybody’s day. I would always advocate using the simplest possible system that will work for your team and doing so until it doesn’t work anymore and then adding complexity only as absolutely needed.

Estimated reading time: 11 min

Rouven Rieker Thoughts about "git-flow" and the Github Flow by a Github employee..

August 22, 2012 | 0

Nils Riedemann recommended Issues with git-flow from scottchacon.com:

GitHub has an amazing code review system called Pull Requests that I fear not enough people know about. Many people use it for open source work - fork a project, update the project, send a pull request to the maintainer. However, it can also easily be used as an internal code review system, which is what we do.

Estimated reading time: 11 min

Nils Riedemann The git flow at github.

October 11, 2012 | 0

Teddy Zetterlund recommended Issues with git-flow from scottchacon.com:

If you deploy every few hours, it’s almost impossible to introduce large numbers of big bugs.

Estimated reading time: 11 min