Details
-
Type:
Suggestion
-
Status: Future Consideration (View Workflow)
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Pull Requests
-
Labels:
-
UIS:356
-
Feedback Policy:
Description
Hi everyone,
Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Server.
We spend a significant amount of time on an ongoing basis to determine our product investments in Bitbucket Server. Unfortunately, we are not currently planning to address this suggestion in the next 12 months. In the last 12 months, we've resolved 10 of the top 30 feature requests, and our upcoming roadmap includes a number of other top voted suggestions, including in-browser editing, improvements to search functionality, better JIRA integration, and providing an even better code review experience.
I understand that this may be disappointing, but we believe it’s important for us to be open, honest and transparent with our customers. Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here.
Norman Ma
Product Manager - Bitbucket Server
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.
Attachments
Issue Links
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
