Say it like this
- I have opened a draft PR for the feature branch
- Let me put this as a draft PR first so the team can comment
- This is still in draft PR status, so changes are coming
Use it at work
Getting early feedback
- I've opened a draft PR so you can see the approach.
- It's a draft PR, so don't review the details yet.
Status
- I'll mark the draft PR ready for review tomorrow.
- The draft PR still needs tests.
Process
- Open a draft PR early to avoid big surprises.
- CI runs on draft PRs too.
Don't say this
The context matters. A regular PR signals the code is ready; a draft PR signals it is not. Be explicit about your intent.
Practice
Try it
4 quick exercises
1. Your team needs to discuss your implementation approach before you finish coding. What do you say?
2. I will _______ this as a draft PR first to get team feedback before submitting for final review.
3. Which sentence uses draft PR incorrectly?
4. Rewrite this in natural tech English using draft PR: 'I put my unfinished code online so the team can give me comments before I finish it.'
Say it out loud
Phrase 1 of 3
"I have opened a draft PR for the feature branch"
We don't save your recording. The word check uses your browser's speech recognition.
More about draft PR
Real examples(3)
- in a standup
"I pushed a draft PR yesterday for the API refactor. Please take a look and let me know if you see any issues."
- in a code review
"This is a draft PR, so I'm still working on the test coverage. Your feedback on the approach would be helpful."
- in a Slack message
"Converting the draft PR to ready now since we fixed all the failing tests."
More mistakes(2)
Handle with care. Do not confuse with simply opening a PR. A draft PR is specifically marked as not ready for review, whereas a regular PR is ready. Avoid using draft PR when you mean work in progress on a local branch.
- ✕This draft PR is ready to merge.✓This PR is ready to merge. I'm converting it from draft status now.
A draft PR by definition is not ready to merge. Once ready, you convert it to a regular PR.
- ✕Can you review my draft PR? I will update it later.✓Can you review my draft PR? I'm still implementing the error handling, but early feedback on the structure would be helpful.
Be specific about what is incomplete and what feedback you actually want. Do not ask for full review on incomplete work.
Other forms(3)
- draft PR noun
"The draft PR is available for feedback on the main repository."
- open a draft PR / create a draft PR verb phrase
"I will open a draft PR to discuss the implementation approach with the team."
- convert from draft PR / mark as ready verb phrase
"Once the tests pass, I will convert this from draft PR to a regular PR."
Often used with(4)
- open a draft PR · to create and publish a draft PR on your repository platform
- convert a draft PR · to change a draft PR status to ready for final review and merging
- mark as draft · to set a PR to draft status when creating it
- draft PR feedback · comments and suggestions given on incomplete code in draft status
Similar words(2)
- work in progress PR (WIP) · older term meaning the same thing; now mostly replaced by draft PR functionality
- incomplete PR · describes the state but is less formal and not the standard term
Opposites(3)
- ready PR
- production-ready PR
- merge-ready PR
Questions(8)
- What is a draft PR on GitHub?
- On GitHub a draft pull request cannot be merged and does not ask code owners for review. When the work is ready you click "Ready for review".
- When should I open a draft PR?
- Open one when you want early feedback on your approach, want CI to run, or want the team to see progress. Say what you want: "Draft PR, mainly looking for feedback on the data model."
- Is a draft PR the same as a "WIP" PR?
- Yes, mostly. Before GitHub added drafts, people put "WIP" (work in progress) in the title. Both mean the PR is not finished.
- What does draft PR mean in software engineering?
- A draft PR is a pull request marked as work in progress or not ready for final review. It allows developers to share incomplete code with the team for early feedback, discussion, and collaborative development before the code is finished and ready to merge.
- How do you use draft PR in a sentence at work?
- You use it as a noun to refer to the pull request itself. For example: 'I opened a draft PR for the authentication feature' or 'Can you review this draft PR and let me know if the approach makes sense?' You can also use it as part of a verb phrase: 'I am going to draft PR this work so we can get early feedback.'
- Is draft PR formal or informal?
- Draft PR is neutral in formality. It is the standard technical term used in both casual team chats and formal code review processes. It is appropriate for all professional contexts in software development.
- What is the difference between a draft PR and a regular PR?
- A draft PR signals that the code is incomplete and not ready for final review or merging. A regular PR indicates the code is ready for final review. Reviewers typically give more exploratory feedback on draft PRs and more critical feedback on regular PRs. Draft PRs cannot be merged until converted to regular status.
- When should you open a draft PR?
- Open a draft PR when you want early feedback on your approach, when your code is incomplete but shareable, when you want to discuss implementation strategy before finishing, or when you need to block time on a feature but the code is not ready for final review.
