Hacker News

points by gz09 6 hours ago | 0 comments

I wish they would instead focus on fixing the regressions with PRs first... For example: There is a nasty bug that got introduced recently where you click "Merge when ready" but your chances of things actually going to the merge queue seem to be only at about 60-70%. When it happens the way you usually find out if things still aren't merged the next day.

Their support has acknowledged the issue to us over a month ago but no fix as of now.

[–] losvedir 4 hours ago

A bug that's been driving me crazy lately is the file list in the sidebar doesn't reliably link you to the right file when you click on a filename. I find myself clicking it several times while the code on the right jumps around until it finally lands on the right file.

Anyone else experience this?

On topic, regarding these changes. I'm not sure what all changed, but I like having the status checks and merge button at the top of the page now.

[–] DrewADesign 4 hours ago

Overall, this isn’t a super great time for software users that value working features over new features.

[–] ambicapter 4 hours ago

I've seen that too. Takes one or two clicks for it to actually scroll to the correct file.

[–] sirfz 4 hours ago

Yes I noticed the same issue

[–] leipert 6 hours ago

Same. What’s even worse is that there is no visibility into it.

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

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.

[–] spike021 6 hours ago

Just the other day my teammate approved my PR and despite the repo having that merge when ready feature enabled, it kept not working and throwing some random error.

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

[–] esafak 5 hours ago

Their workflow scheduler is broken too. I noticed that workflows were getting scheduled hours late or not at all, so I had my own workflow orchestrator trigger them.

[–] cadamsdotcom 5 hours ago

Publication of a completely unrelated article while another team is failing to fix that bug is a side effect of the company having more than one employee.

Companies with more than one person also have the issue that people don't communicate 100% of what's going on. This means prioritization is imperfect so they often do things other than what you'd like them to. Also you'll find different cultures which differently emphasize fixes and new work.

Hope you're not having too bad of a week whule your bug persists.