Post

we out here using mailing lists dawg catch up

Hi can you let us reorder them? :)

Also reviewing by-commit makes you experience more page loads which is quite annoying (especially since it feels like something in the github code that tries to make them faster makes them slower instead, I often end up reloading the page immediately after clicking on a link to make it faster...)

Okay. Stellar might be an overstatement. But quite a lot better than what Azure DevOps has to offer. 🙂

you assume people still review code (they do not) but good news, stacked PRs lets you stack even more changes and pretend anyone still reviews them 🤪👍

potentially obsolete commits is insane

Not sure about stellar, I appreciate that GitHub shows me what changed since I last reviewed. Sometimes 😅 And then I don’t know how to get that view back. But the per-commit wouldn’t be good because most people are no good at separating their commits, which breaks my heart… I love a good history.

My experience is that learning to divide up your PRs into proper commits not only make the PRs much easier to review, but it’s also a great tool for upping your coding skills. And recently I have also seen Claude use these atomic commits to better understand the code. Pretty cool.

did y'all fix the bugs with squash-merging yet? does that work?

tiny diffs. one dependency graph. the approval on top should not survive the basement moving.

TikTok-style ad Et tu, Brute?

Lovely!

let’s goooooo

ignoring this like a queen

What the hell is that website, it keeps opening the video over and over, even when I turn on reader mode.. I felt like I was escaping a malware rather than learning of an interesting sounding new feature.

Congrats, but this video motion is going to cause epilepsy in some viewers.

And a seizure 😅

The only issue I’ve hit is when GH merges changes into an intermediate branch I often need to check out fresh copies of my local branches. This happened as things get reviewed and updated. I feel like I’m missing something though, but haven’t had time to dig into the recommended workflow.

finally. the real test is whether dependent PRs stay painless once rebases and merge queues enter the picture