The first PR comes from @benbridts. 
I suppress my reflex of smashing the Merge button sight unseen and actually read it.
Well that's embarrassing. I briefly contemplate fixing and rebasing main, then asking him WTF he's talking about, but that would be petty.
Well that's embarrassing. I briefly contemplate fixing and rebasing main, then asking him WTF he's talking about, but that would be petty.
Feature request for @github: I wish I could leave a comment while merging. I always wonder "comment then merge, or merge then comment?" I'd prefer one button click to two.
The next PR comes from Ben Abineri. "Ben." I just called you "Ben."
Oh dear. That's embarrassing! I'm not using this to track @senatemajldr's Twitter followers, so that should get fixed immediately.
I always make it a point to leave a comment thanking the contributor unless it's me. They bothered to send a PR, you can bother to say "Thank you."
A third has shown up, from @sogrady. It's a belated Hanukah miracle! There might be enough Pulls Request for eight nights after all.
Wait I just fixed this. Did I typo it twice?!
At this point I stop playing with @GitHub and use the git CLI as God intended.
At this point I stop playing with @GitHub and use the git CLI as God intended.
No, same typo. Why is @github not showing a merge conflict here against the stale PR?
Incidentally, a "merge conflict" is the proper collective noun for developers.
Incidentally, a "merge conflict" is the proper collective noun for developers.
Yeah, the PR vs what's currently on Main. What on earth? There's clearly something I'm not understanding.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
