Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How is this in any way better or simpler than Git Flow? IMO Git Flow is conceptually easy to understand and easy to implement. Using it on a pretty decent sized team (40+ developers) and it works great for us - and is easy for newcomers to the project to pick up.


This essentially IS git flow.

Edit: Never mind, I wasn't remembering git flow correctly.


This is most definitely not git flow. Git flow advocates explicit merges pretty much everywhere with no fast-forwards and definitely no rebasing.


Rebasing locally before "publishing" (pushing) changes to the central repo is definitely okay. It should always be done before pushing the branch for the first time, really, because if someone else has modified develop since you started your branch, you want to make sure your changes are still working and won't break the build (on develop).


You're right, it's not. I need to stop commenting on HN before I've had coffee. :/


Is there a link where I can read up the type of Git flow that you are talking about?





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: