Draft Pull Requests
Draft PRs are a valuable tool for teams to collaborate early in the development process and maintain clear differentiation between work-in-progress and ready-for-review pull requests.
Draft/WIP (Work in Progress) Pull Requests
Draft pull requests (PRs) are a methodology used during the development process to gather early feedback from other developers and take advantage of CI systems integrated with the Git provider. Unlike regular PRs, draft PRs signal that the work is not yet ready for review or merge and is still part of the coding stage.
Supported Platforms
- GitHub and GitLab: Fully support draft PRs.
- Azure Repos: Draft PR status is fully supported and can be reported via their API.
- Bitbucket: Does not support the concept of draft PRs.
Behavior of Draft PRs in LinearB
- Cycle Time Calculations:
- Draft PRs are excluded from cycle time calculations.
- Time spent in the draft state is attributed to Coding Time instead.
- Notifications:
- Draft PRs do not trigger notifications for "Review request hanging" or "Review too long."
- Visual Indicators:
- Draft PRs are visually distinguished by the "Draft" status on the Branches and PRs pages.


Configuring Draft PRs in LinearB
LinearB automatically detects draft PRs based on their status in supported platforms. Additionally, you can configure specific PR naming conventions to be treated as draft PRs.
Steps to Configure:
- Go to Company Settings > Advanced.
- Scroll down to the Draft Pull Requests section.
- Enter regular expressions to define naming patterns that should be recognized as draft PRs (e.g., "WIP" or "Draft").
- Click Save.


Draft PRs are a valuable tool for teams to collaborate early in the development process and maintain clear differentiation between work-in-progress and ready-for-review pull requests. With LinearB's enhanced support, including Azure draft PRs, teams can ensure accurate metrics and streamlined workflows.
How did we do?
How does LinearB handle squash merges?