I use WIP bot wherever possible, never touched draft PRs. I much prefer the simplicity of having โ๐งโ at the start of the title and then the pending bot check over the draft PR UI.
Native Android developer/Consultant for Appwise, I work on custom projects for clients.
PHP/JS (web) developer in my freetime. Trying to keep learning in an ever changing tech world.
But there are benefits that draft PRs have that WIP bot can't provide.
There are multiple visible indicators that it is a draft PR, WIP is limited in this.
Draft PRs can't be merged, WIP bot can't block merges.
If you have a CODEOWNERS file in your repository, a draft pull request will suppress notifications to those reviewers until it is marked as ready for review.
There are multiple visible indicators that it is a draft PR, WIP is limited in this.
I honestly prefer having the single indicator of the ๐ง emoji in the title.
Draft PRs can't be merged, WIP bot can't block merges.
It can... have branch protection rules in place that require all checks to pass :)
If you have a CODEOWNERS file in your repository, a draft pull request will suppress notifications to those reviewers until it is marked as ready for review.
Never personally worked on a project with code owners, either manually requested views or had a bot that requests reviews once all checks pass.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I use WIP bot wherever possible, never touched draft PRs. I much prefer the simplicity of having โ๐งโ at the start of the title and then the pending bot check over the draft PR UI.
But there are benefits that draft PRs have that WIP bot can't provide.
I honestly prefer having the single indicator of the ๐ง emoji in the title.
It can... have branch protection rules in place that require all checks to pass :)
Never personally worked on a project with code owners, either manually requested views or had a bot that requests reviews once all checks pass.