-
Suggestion
-
Resolution: Unresolved
-
None
-
27
-
Hi everyone,
Thank you for your feedback. We appreciate your input and understand the importance of addressing our users' suggestions. Unfortunately, we don't have plans to address this specific suggestion in the next 12 months.
However, I want to assure you that your feedback is valuable to us. Over the last 12 months we have successfully implemented many highly voted suggestions including code-owners, resolvable comments and auto-merge and our upcoming roadmap includes a number of other top voted suggestions including 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.
Once again, thank you for sharing your thoughts with us. Your feedback plays a crucial role in shaping the future of our product. 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 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.
- relates to
-
- Closed