Comments by "p11" (@porky1118) on "Why CI is BETTER Than Feature Branching" video.

  1. Also when working alone, branching is sometimes useful. I've already done it a few times.
    9
  2. In general I'd agree, but in some cases it still seems useful to branch to me. Especially when doing some more experimental stuff, where you don't know, if you even want to add this change. But if you already know, you're going to merge this branch/feature sooner or later, it's always better to merge it now. It's much worse, when others already depend on a feature, which often changes, than when you are not able to merge this feature anymore. And you will always be able to merge your feature in most cases.
    4
  3. If you haven't compiled your project on a normal work day at least once, something is already wrong anyway, I'd guess.
    4
  4.  @timothyblazer1749  In most VCS merges are more complicated than they need to be. Git for example always needs a merge commit if you merge something which is not just a fast forward. In Pijul, which is still in development, you only need a merge commit if two changes change the same line of the same file. And merge conflicts should appear less often anyway.
    1
  5. But that's more of a problem when doing CI. When everyone is pushing on the same branch, up to every second commit is a merge.
    1