-
Suggestion
-
Resolution: Unresolved
-
None
-
67
-
Hi everyone,
Thank you for sharing your thoughts and voting on this suggestion. We agree that this would be a valuable addition to Bitbucket Data Center, but at this stage it is unlikely that we will be able to implement this idea in the next 12 months. So, what are we doing instead? Over the past year, we have addressed many of the highly voted suggestions such as codeowners, resolveable comments, and auto-merge. Our upcoming roadmap also includes several other top voted suggestions such as dark theme, draft pull requests, and multi-line comments. For the most up-to-date information on what features are coming soon please visit our roadmap.
We do continually review these priorities and will continue to do so over the coming year to determine when and how we might be able to address this idea. You can learn more about our prioritization process here.
Cheers,
Sarah Bolt
Product Manager - Bitbucket Data Center
Original request description
If pull request was approved and merged by wrong decision then we need to rollback it and re-open Pull Request. To do this git has full support:
http://git-scm.com/2010/03/02/undoing-merges.html
You should used git revert -m 1 <hash>
After this Stash can automatically reopen Pull Request from receive hook. And work with Pull Request as it has not been merged yet. Then merge it again and all be fine from Git side.
- is duplicated by
-
BSERV-4343 Ability to undo (and re-open) the merge of a pull-request
- Closed
- relates to
-
JRACLOUD-43105 Automatic transitions triggered by Stash should allow more advanced conditions and actions
- Closed
-
JRASERVER-43105 Automatic transitions triggered by Bitbucket should allow more advanced conditions and actions
- Gathering Interest
-
BBSDEV-26271 Loading...
-
BBSDEV-26727 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...