Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
88
-
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 Data Center.
We spend a significant amount of time determining our product investments in Bitbucket Data Center. Unfortunately, we are not planning to address this suggestion in the next 12 months. In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request description templates, capability to enable/disable source branch deletion on merging pull requests and our upcoming roadmap includes a number of other top voted suggestions, including repository archiving. Please check out our public roadmap for more details on the coming soon and future items.
I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.
Cheers,
Anton Genkin
Product Manager - Bitbucket Data Center & Server
Original suggestion
The main use case is for a pull request to merge a hotfix branch into master(following the pattern described at http://nvie.com/posts/a-successful-git-branching-model). After it's merged, I want to tag the merge commit in master with a version. I would like to be able to supply a tag name to apply to the merge commit when I click the merge button on the pull request.
Attachments
Issue Links
- relates to
-
BSERV-2491 Add Git Flow (branching) support
- Closed