70
ars1
17d

That co-worker that erases all of your changes if there's a merge conflict.
Fuck you too buddy.

Comments
  • 3
    WTF people usually fixes merge conflicts
  • 7
    There has been 1 or 2 times where I accidentally removed my coworker's merge fixes. I told him right away and sat on a call to put it back. It was my fault
  • 2
    Especially when you did code in an attempt to make things better for him and his friends 😆 not familiar in any way.

    Damn you Vietnamese guy I've never seen before
  • 3
    The problem with git is that far too few developers take the time to understand the value proposition.

    Turning git into a Last-In-Wins system is a common example.
  • 0
    I don't see how that is even possible: your merge would be refused due to failing tests in the pipeline. You guys have tests right? Right??
  • 2
    @SuspiciousBug there are tests (that i insisted on adding), but it's not part of the pipeline yet so you have to run them by yourself. Project is still new but I'll be looking at that once I finish a couple other features.
  • 3
    @SuspiciousBug forgot to mention that the merge deleted most of my tests anyway lol
  • 0
    @SuspiciousBug in my case it was UI (xaml) related, and even if i would have written tests, i bet they would have been commented out too 😂
  • 0
    Yep happen to me too..
  • 0
    Sometimes erasing it just doesn't cut it. It should burn the author writting stupid code.
    Not saying yours was bad. But you know... when you see that no thought went into it and it's just wrong no matter how you analyse it.
Add Comment