Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
2
-
Description
The "Merge" button is not available until the all conditions are satisfied. Bitbucket is already checking for the status of the builds, approvals, and can show this information visually. It would be nice if once all conditions updated to allow the "Merge" button, that it automatically merged the Pull Request for you.
My common scenario is, "Minimum successful builds" is enabled, I have everything ready, and I get the required "approvals". The build takes more than an hour, so I wait for the "build email", and then go back to click the "Merge" button in BitBucket. Well, sometimes, I have left for the day. When, I click it first thing the next day, there is more than an hour delay for an "official" build.
How to make this happen? Allow the ability to configure the "merge commit message" ahead of time - perhaps when creating the Pull Request. Also, allow it to be updated up until the last minute. In my case, I like to add a "Reviewed by Person1" in the commit message to make that easier to see in the commit history.
So, expose the existing "Merge commit message" earlier - at Pull Request creation.
Add a new checkbox, to automatically merge the change when all "merge criteria" are met. I'm not sure if it should default to "False", to keep the old behavior, or not. The majority of users might expect this to happen and desire it. Maybe default to "True".
That should satisfy this work flow, and for those that are not around when it gets all the approvals as well as a build or any other conditions, the Pull Request may be automatically merged if configured.
Attachments
Issue Links
- is duplicated by
-
BSERV-11946 Merge-when-ready button
- Closed
- relates to
-
BSERV-12214 notification when pull request is ready to merge
- Gathering Interest