4 ms·
Seems to mainly be useful for monorepos as currently designed. Or, to replace a long-lived feature/refactor branch.
by ZeWaka 6mo ago
Seems to mainly be useful for monorepos as currently designed. Or, to replace a long-lived feature/refactor branch.
- YesThatTom2 6mo agoWhatbmakes you say that? Devs use stacked PRs in small and large repos today.
- ZeWaka 6mo agoTheir examples show combined backend and frontend changes on the same monorepo in different PRs. As far as splitting work into different PRs that need coordinated merging, I've only ever encountered that when it's a long lived refactor / feature.
- Hamuko 6mo agoI think the only thing I miss from GitLab was being able to make merge requests depend on other merge requests, even across repositories. So I could make a backend repository MR depend on a library repository MR, and even enable auto-merge that’d fire when the backend MR was reviewed and the dependency was also merged.