In my experience, stacking a big feature in multiple small pull requests plays well in order to start reviewing and delivering work that can be merged mainline

In my experience, stacking a big feature in multiple small pull requests plays well in order to start reviewing and delivering work that can be merged mainline while building more parts of the feature (say, sending for review a service object or an API client while you are working on the controller for that service), and it is easy to do with any Git client. However, it starts to erode when a change in one of the initial layers has effect on others, such as having to make a change in the service layer that affects the way you pass a parameter in the upper layers. Then you find yourself just doing a rebase nightmare to keep the whole set of PRs in sync. I wonder how many companies or teams would consider paying 30 bucks a month per user just to solve this problem.