Ask HN: How do you incrementally stage PRs for a larger feature in Git/GitHub?

I like to keep my PRs small. Incrementally rolling out a larger feature to main gradually. Usually indicating the larger direction in the PR, but showing how this PR is an earlier stage of a larger plan.

The small PRs are easier to meaningfully review. Nothing sucks more than getting a giant 10k line PR to suddenly review and pretend to have meaningful input about.

But the show must go on. I must continue to develop my feature at step N+1 while colleagues take time to review the PR at step N.

I wanted to check with other devs - how do you personally do this?

- Do you create a branch off step N for step N+1?

- Do you keep a feature branch and gradually merge segments to main when they're ready?

- Do you wait for a merge to main, and nag people?

I personally often do the latter, get things into main. And find other non-dev work to do. But often this takes a hit to my momentum behind a feature. Yet if I get too off on a branch without feedback/input I could end up wasting my dev time if I go to far in a direction that turns out not to be agreeable with the team.

Are there any documented best practices / methods / workflows for using git (and version control in general) to manage this?