5

Waiting to merge the rest of the team’s new code because you don’t want to deal with migrating your test account to a new backend until your feature’s ready, finally finishing your feature (!) and then seeing 100+ merge conflicts and realizing you‘re better off just re-implementing all your feature code into a new branch, & deleting every trace of your old branch so nobody sees the 1000+ merged commit mess you’ve made -_- today was supposed to be easy...

WHY WOULD ANYONE NEED THREE DEPENDENT SUBMODULES ANYWAY?!?! 😩

Comments
  • 2
    I have projects that depend on more than 10 submodules. Just like a library, if more than one project uses code, reuse it.
    You don't want to have to manually build a library and export the bin every time to update it. Just pull latest changes.
Add Comment