I like to do it as a way to get feedback on code before it's ready.
I'll open a draft PR, then my teammates can comment on specific lines of code. The entire discussion stays in one thread.
For larger changes, I've also used it as a way to communicate progress. I'll open a draft PR, and then write out a check list showing what's done and what isn't. Then anyone following along is able to see where I'm at with the project. 😃
I like it, but I do not understand why you should even open a pull request before you are ready to merge changes.
ooh, I have lots of thoughts on this! 😃
I like to do it as a way to get feedback on code before it's ready.
I'll open a draft PR, then my teammates can comment on specific lines of code. The entire discussion stays in one thread.
For larger changes, I've also used it as a way to communicate progress. I'll open a draft PR, and then write out a check list showing what's done and what isn't. Then anyone following along is able to see where I'm at with the project. 😃
I see - you mean if you have some changes you want to be reviewed but you do not want it to be merged because you aren't done yet.