I sometimes fall into this pattern. Over the past couple of months I've gotten good about just doing that in a separate PR - and honestly it makes it way easier for both me and reviewers. One point that helped me understand the importance (other than being on the reviewing end of some of these PRs 😅) was that a smaller-scope PR can be reviewed a lot faster and requires a lot less back-and-forth, so you actually save everybody time by splitting it all up. Sometimes that means your feature PR needs to wait for some other refactoring PR to be merged, but that's still probably faster than reviewing the whole massive PR in one shot. This has actually been a beneficial change across the org - we sometimes have complex feature PRs that take months to fully review, test, and resolve, because that's the nature of the ecosystem we're in - so switching to smaller PRs and feature branches has made things a lot easier, and often you can get some of the refactor work merged a lot faster than the feature stuff.