a great workflow to ensure you maintain constant ever increasing
version numbers with enough room to fix mistakes. The downside is the
slowness of deploying new features. GitFlowSimple is a simplified
version which can be expanded to standard GitFlow when needed, but is
less effort when deploying new features.
Normally, I would just use GIT without a bridge to another control
system, but many companies use SVN. There are just so many benefits
to using GIT that, for me, I am going to use it if there is a bridge
to repository type the company uses. I certainly don’t hate SVN or
CVS or Perforce, but GIT allows me to work the way that I know I am
most productive; which is commit early, commit often.
What I mean by commit early, commit often is that I commit even if I
only have part of the solution. As I find the other parts of the
solution I commit those as well. That way when I am 2 or 3 days into a
fix I already have the commit messages saved in GIT, so I don’t have
to remember what I did for those 2 or 3 days. When the solution is
shippable only then do I push it up to the company’s repository.