Hacker News new | ask | show | jobs
by IshKebab 3 hours ago
I agree, these things just seem to add too much mental complexity compared to the advantages. Even the sign-up process is wierd, e.g. I put in my username as `dave` but if you try to log in as `dave` it says "did you mean dave.tngld.sh?" What? Then when you log in it takes you immediately to a second OAuth screen where you have to put your password in again, immediately after you logged in. I'm sure they would try to justify this bad UX with technical reasons...

I think the main attractive thing about Tangled is that it supports proper stacked PRs. But on the other hand it doesn't support private repos at all, and Github is getting stacked PR support soon (fucking finally)...

It's hard to see the advantage of Tangled over Codeberg for example.
1 comments
sshine 3 hours ago
It seems like Forgejo isn't actively planning to have stacked PRs:

https://codeberg.org/forgejo/design/pulls/48

Which is totally understandable.

Managing a healthy highly-popular open-source codebase requires effort to not bloat it.

Which brings me back to wanting good APIs for native Kubernetes CI runners and time-limited PATs for agentic coding.

I can vibe that in a day. But it sure as heck won't be aligned with the future of all Forgejo users.

link
IshKebab 3 hours ago
> Which is totally understandable. > Managing a healthy highly-popular open-source codebase requires effort to not bloat it.

I would not call stacked PRs bloat. It's a super important workflow. The fact that Github hasn't supported it for so long is insane.

link
sshine 12 minutes ago
It’s not bloat.

The argument is maintainer bandwidth/fatigue.

From the closed issue:

> Closing this out for the time being, as noted previously (I'm currently leaning towards designing some review refinements and shelving the stacked concept design for the moment) and to clarify that it isn't current and active work.

link