3 ms·
> 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
by IshKebab 5mo 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.
- sshine 4mo agoIt’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.