We are using the WIP bot in combination with draft prs.
Example:
- We create
draft prs and start developing something
- If it is ready for review we convert the pr to
ready-for-review
- We might set the
do-not-merge label, because we want to block the integration for a given time (using the WIP bot)
Problem:
The combination of draft prs and the WIP bot results in strange combinations that might be confusing to the developers, see:
Solution:
Having a location field pr_status that checks for the pr status and will fail for draft prs would be beneficial, so that the both status are in sync.
We are using the WIP bot in combination with
draftprs.Example:
draftprs and start developing somethingready-for-reviewdo-not-mergelabel, because we want to block the integration for a given time (using the WIP bot)Problem:
The combination of
draftprs and the WIP bot results in strange combinations that might be confusing to the developers, see:Solution:
Having a location field
pr_statusthat checks for the pr status and will fail fordraftprs would be beneficial, so that the both status are in sync.