11

*working at a project, currently creating commits and pushing to remote

I created an early PR with a title [UNFINISHED] and [NOT YET DONE]. I'm really not finished yet. lots of stuff still need to be committed and pushed to repo

And suddenly, I find out that my team mate - just out of the blue without any prior warning - MERGES THE PULL REQUEST

"oh hey there are conflicts in the pr you made"

YEAH WELL MAYBE TRY GETTING YOUR HEAD OUT OF YOUR ASS WHAT IS WRONG WITH YOU ARE YOU EVEN SANE

So now what happened is half of my commits are merged, he didn't tell me, i pushed more commits, branch recreated, and then he reverts the merge. so now everything is really messed up :)AS)D(F)AEF)SDF)AW)sfdjsigkl;zfghlkkj ghaslkj;gabsd;lkgjabslkfgh GET YOUR HEAD OUT OF YOUR ASS I WANT A PROMOTION

Comments
  • 1
    @DLMousey just pasting my comment here

    Okay. I agree, although my motive was to get early reviews for the part of the work that I've finished and just to let them know my plans, yes why open a pull request if it wasn't ready yet. But how about this:

    1. I didn't even add her as a reviewer.

    2. WHY WOULD YOU MERGE EVEN IF THERE WERE 0 APPROVALS

    3. BITCH ANSWER ME

    4. ANSWER ME

    5. NO ONE TICKED APPROVE AND YOU MERGED

    6. That's not her. 100% sure.

    A pull request, you can just ignore especially if YOU WEREN'T ADDED AS A FREAKIGN REVIEWER

    But to merge OUT OF THE BLUE even if you DON'T BELONG IN THE PR and then COMPLAIN THAT IT HAS CONFLICTS

    I do have a problem with that.
  • 1
    LOL. I wonder what branches are and how they work?

    PRs are for merging. If you need to do work, make a branch. When the branch is feature compete, make a PR.

    Let me guess: your trash can has gigabytes of files in there, because you use it as a temporary holding space.
  • 1
    @Lemelle-Bravo check out the comments here maybe you'll learn a lot more https://devrant.com/rants/1894940/...
Add Comment