Became so bad for us that we switched to an external merge queue provider (trunk.io)

P90 of merge queue entry _started_ dropped from up to 40! minutes to 16 seconds. And it’s the same underlying mechanism, creating a branch and running CI on it.

IIRC we unapproved it, approved without that enabled, and then manually merged it.

Companies are rarely monolithic and are made up of more than one person who often don't communicate with one another and often don't do the exact things you'd like them to - and often have different cultures which differently emphasize fixes and new work.

Hope you're not having too bad of a week as a result of your fix not landing fast enough.

Anyone else experience this?

Why not fix the garbage UI first?

If we could just see unresolved comments and CI status in a page that take 100ms to load and 1 second to scroll to the bottom, everything would be fine.

The problem is that it the PR Conversation page takes 20-25 seconds to load a scroll through; and is full of outdated reports from Copilot/ Devin that don't go away of themselves, and don't have a good UI to be dismissed, once they're irrelevant.

I'm outside the US so poor UI <-> server network interaction may be magnified. But for something that could be simple and reasonable, it's just overloaded with garbage and an appalling experience.

Fix the basics first. I'd fire the entire team and every single Product Manager/ UX Lead involved. Anybody from Github listening?