I think what OP did is poor practice. From the maintainer side, how are they supposed to know when the PR is ready for review? Are the maintainers expected to keep checking in on the contributors' threads with themselves to make sure everything is wrapped up?

To me, there's two things you can mean with a PR:

- Open a normal PR: I personally attest to the quality of the code, and I'm ready for the maintainer to review/merge it.

- Open a draft PR: I have questions about proceeding and want to show you a work in progress to give context.

Any kind of intermediate work to prepare it for the maintainers should happen in a fork, not adding noise in the official repo. When you're done experimenting in the fork, then it can go to the main repo.