| Info |
|---|
For Bitbucket >= 8.18, the apps' Draft feature is super seeded by the native Draft support. |
Creating a pull request should not always happen when your changes are fully ready. Sometimes you want to create a pull request as soon as possible (while its state is still work-in-progress), so that you can engage the discussion early on with your teammates.
...
When creating a pull request, you can decide to mark your Pull Request as Draft by clicking on the “PR Draft” “Draft” button in the Code Owners section.
...
Once you are satisfied with the state of the pull request, you can mark it as Code Owners: Ready for review. Review (un-draft) When you do so, all Code Owners will be added automatically. This assumes that you have the auto-assignment enabled, which is the default. If it has been disabled, you can re-enable it via the addon setting.
To mark a pull request as being Ready for review, you can click on the contextual menu on the top left, then click on the “Ready for review” “Code Owners: Ready for Review (un-draft)” button.
...
Benefits of Draft Pull Requests
...
When you create a Pull Request as a draft, Code Owners are not automatically assigned as reviewers. This prevents unnecessary notifications and noise for Code Owners who might otherwise be inundated with review requests for work that is not yet ready for their attention. By giving Code Owners the flexibility to focus on fully ready Pull Requests, you can help them prioritize their time and efforts more effectively.
Incremental Feedback and Iterative Development
Draft Pull Requests enable an iterative development process by allowing you to receive feedback in smaller increments. Instead of waiting until your changes are fully complete before seeking review, you can share your work in progress and receive early feedback on specific aspects of the codebase. This iterative approach promotes continuous improvement and helps identify potential issues or improvements earlier in the development cycle.
...