Comment on The forge we deserveparentComments−sshine2moIt seems like Forgejo isn't actively planning to have stacked PRs:https://codeberg.org/forgejo/design/pulls/48Which 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.−IshKebab2moWhich 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.−sshine2moIt’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.
Comments
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.
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.
It’s not bloat.
The argument is maintainer bandwidth/fatigue.
From the closed issue: