Comments by "p11" (@porky1118) on "Git Flow Is A Bad Idea" video.

  1. Isn't it a good workflow to merge develop into your feature branch at least once a day? It's similar to CI, but other people won't be disrupted by having to relearn changes of an unfinished feature. For example, I rename a method and add a few similar methods and then remove some, I don't want to be used, after I'm sure, which are the best methods. If I do CI, everyone has to learn the new methods, if they need one of them, and maybe they use one, I want to remove later, but can't anymore because it alreaty has been used. So I just merge the develop every few hours, so I see, nothing breaks, and when my feature is finished, I merge it to develop.
    2
  2. Isn't it a good workflow to merge develop into your feature branch at least once a day? It's similar to CI, but other people won't be disrupted by having to relearn changes of an unfinished feature. For example, I rename a method and add a few similar methods and then remove some, I don't want to be used, after I'm sure, which are the best methods. If I do CI, everyone has to learn the new methods, if they need one of them, and maybe they use one, I want to remove later, but can't anymore because it alreaty has been used. So I just merge the develop every few hours, so I see, nothing breaks, and when my feature is finished, I merge it to develop.
    1
  3. I tried to establish this branching scheme with master, develop and feature branches, but it didn't really work. Most of the time I couldn't even stick to it myself.
    1