Does Converting a GitHub PR to Draft Free Up Your Limit?
An unfinished PR is now a draft, but GitHub still won't let you open another one in that project. Why does the maintainer's cap still count it?
- Repositories can include drafts in their open-PR limits following GitHub's October 8 update.
- The cap applies to contributors without write access in public repositories.
- Archiving also hides a PR and makes it read-only; choose it for moderation, not merely as another name for closing.
A draft can still occupy a place under the cap
GitHub's October 8 update lets maintainers include draft pull requests when limiting concurrent contributions. Previously, drafts were excluded even when ordinary open PRs were capped.
When Count draft pull requests toward the limit is enabled, converting an open PR to draft leaves it in the count. With the option off, only open, non-draft PRs count. The change introduces a configurable choice, not a universal rule that every repository now counts drafts.
Maintainers can allow exceptions without granting write access
The repository interaction settings place this control under Settings → Moderation options → Interaction limits → Pull request limits. Choose the concurrent maximum and whether drafts belong in it.
This cap concerns contributors without write access to a public repository. People with write access or higher are unaffected. It is neither a repository-wide total nor an API rate limit.
A Bypass list allows trusted external contributors to exceed the cap while preserving their existing permissions. That is useful when someone needs several parallel PRs but does not need permission to modify repository code directly.
Resolve an existing PR or discuss a bypass
Once you reach the cap, an existing PR needs to be closed or merged before you can open another, unless a bypass applies. Review which work is still active before choosing a PR to close. If several ongoing contributions belong together, discuss the limit with a maintainer instead of assuming that marking one as a draft will release a place.
Draft status communicates review readiness. With draft counting enabled, it does not reduce the number of open contributions. Keeping those two roles separate makes the next step clearer for both contributor and maintainer.
Archiving changes visibility as well as status
Archiving closes a PR, removes it from public view and preserves its history for people with triage access or higher. The conversation becomes read-only, blocking new comments, reactions and automated comments even from administrators.
A second October 8 change lets triage, write, maintain and admin roles archive and unarchive PRs. Use Archive pull request at the bottom of the right sidebar when hiding the contribution is the intended moderation action.
Authorized users can find archived PRs with is:archived. Unarchiving restores visibility and conversation activity but leaves the PR closed; reopening is a separate step. A legitimate contribution that only needs its work concluded and a spam submission that should disappear from public view call for different decisions.