Coding & Git

Draft PR

Also called draft pull request, draft pull requests.

A draft pull request is a pull request shared as work in progress. GitHub's docs say it cannot be merged, and code owners are not automatically asked to review it.

Example

You open a pull request as a draft so a teammate can see the branch early. They can read the changed files. GitHub will not merge it while it stays a draft. You mark it ready for review when you want code owners requested.

Why it matters

GitHub's pull request docs say that when you create a pull request, you can make it a draft. Drafts are for sharing work that is not ready, without formally requesting reviews. When you want feedback, you mark the draft ready for review, and that requests reviews from any code owners. You can convert a pull request back to a draft later, for example when comments mean more changes are needed. Nobody can merge it until you mark it ready for review again. People already subscribed to its notifications stay subscribed when you convert it to a draft.

A draft pull request is still a pull request. It points at a branch and at commits. The draft stage says the page is not ready to merge. It does not erase the commits.

How it shows up on bot.ski

On bot.ski, the Pull request and Draft glossary pages are the neighboring ideas, and the Git guide explains how to read a proposed change. The public site does not list pull requests. Opening this page does not open one and does not merge one.

Common confusion

A draft pull request is one stage of a pull request. The glossary word Draft is any work that is not finalized, including an unsaved note. The Git tip is the newest commit on the branch, and that commit can sit inside a draft pull request. Marking the pull request ready for review does not deploy a website.

Sources

Updated October 3, 2026.

Cookie preferences