https://bitbucket.org/blog/a-new-status-for-pull-requests-in-bitbucket-cloud-changes-requested
I'm finding the PR UI changes to support this feature to be non-intuitive. Changing the grey background to blue when you click Approve doesn't really convey you've approved the PR, but then the Request changes button goes away, so I guess so?
At least change the button text to "Approved".
Also, I generally Approve PRs and then Merge, and it's annoying that I now have to go dig it out of the ... button menu.
Perhaps if merge conditions are met, display the Merge button?
I'm super happy someone made a new button for us, but don't hide a button that's going to get WAY more use just to make sure we know there's a new button available.
Brandon, thanks for the quick changes on the button.
Sadly, now I get to gripe about the file list change. The list/treeview toggle is cool, but give us an option to put it back into the Details tab.
Hi @Sean Lively, thanks for this feedback.
I agree with the button text changing when the buttons are selected. We'll have a change out shortly for "Approve" to become "Approved" when set and likewise for "Request changes" to become "Changes requested".
We're also considering your feedback for merge button placement for PR reviewers in conjunction with some other feedback we've seen. Our general stance is that merging is a primary action for authors while requesting changes is a primary action for reviewers and there is limited permanent real estate in the title bar, but we're aware that there are many cases where reviewers regularly merge pull requests and we're discussing what the right solution for that will be.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.