Nevermind. I was confused because admin page said "The Tag Maker" add-on was incompatible and disabled, but it was actually active in my Bitbucket 4.7.1 installation, and I confused it with your implementation. (I should probably file a bug!) The tags UI that you've done is very minimal and nice. Thank you.

If you really wanted to hammer home the distinction between annotated and non-annotated, one idea would be to dynamically adjust the submit button so that it toggles between <Create Tag> and <Create Annotated Tag> based on whether the "description" box has any content or not. That could help users understand what's going on a little more deeply.

(Frankly the whole "annotated" vs. "lightweight" tag thing in Git is a pointless distraction and a design flaw from a usability point of view, but it is what it is, and we have to live with it.)

g.sylvie.davies1687549270
I am from the design team on Bitbucket Server, could you expand on why specifically a checkbox? The current behaviour of creating a tag is that if you type anything into the description, it will automatically become an annotated tag.

A checkbox to toggle whether tag is annotated or not would be nice.

Bitbucket Server 4.7.1 has been released today and allows users to create and delete tags: https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Server+4.7+release+notes

+1

+1

+1

+1

Yes please! I like to do this for release branches, once the release is complete and stable.

+1

I want tag request feature on stash!

FYI all, there is a Jira issue specifically for tag creation during pull request merge: https://jira.atlassian.com/browse/STASH-3737. May be worth voting there as well.

vmascare, sorry but the API for tag creation and deletion was added in Stash 3.7.1 (STASH-4128) You'll need to upgrade to use it.

Is this API available for Stash v 3.3.1?

+1 @Daniel Haskin for "tag option on merge"

This functionality should be native to stash - if your stash servers are very restrictive it's difficult to use plugins

Git flow requires that a tag be put on the master branch whenever merges happen to it. It would be neat to have a checkbox when making a pull request which adds a tag to the merged branch for this.

We developed a plugin for creating tags from Stash, you can find it on the marketplace
https://marketplace.atlassian.com/plugins/be.contribute.atlassian.stash-tagging-support

I would second the suggestion that the PR merge dialog include the option to add a tag. This would dramatically simplify our workflow, and allow us to do releases from within the Stash web interface.

it would be especially nice to create that tag as part of a branch merge after a pull request

It will be good to add a tag from Stash UI, as an administrator before important/major commits. I vote up for this feature.

Vote to allow deleting tags through Stash UI. Thanks for the reference on how to do it CL though.

Another vote for this one. Tags are an important part of our automated deployment process.

casey1, you can delete a remote tag using git...

git tag -d 12345    # remove locally 
git push origin :refs/tags/12345    # remove from remote

On a related note, please make it possible to delete tags from within Stash. We tested creating tags and pushing them to Stash - they now show up there but we have no means to delete them.

When implementing this, please add a hook so that plugins can reject attempts to do things like delete tags (similar to what has been asked for in STASH-4270 for branches)

Adding another vote for this feature. This is important to our workflow.

Agreed, would also like to see this. Commented in STASH-2795 (Show tags in commit listing) about it before finding this thread.

This is a very central feature to most Git workflows. I'm surprised that it's not been implemented.

This is an important feature for me. I plan to have repositories that can only be updated via a pull request and need to tag releases so that my deployer works with a known point in time. It looks like the only way for a tag to make it into a repository is with a client-side git tag / git push. This of course violates my plans to have "gold" repo's that are updated through pull requests only. 2nd, it doesn't appear that pull requests can source off of tags or even considers tags when fulfilling forks/pull requests. My need seems at odds with the "minor" priority of this ticket.

This is indeed a needed feature. After merging branches via a pull-request, add a tag to the release line is useful.

For our git workflow it would be great if it's possible to add a tag when merging two branches after a pull-request.

And, while adding to the interface, please add to the API too.

Whenever we make a build available for manual testing and also when we release, we tag the repository with version and build name
so that we have a human readable way of finding the source code state to a specific release. This is standard procedure for the
build manager and it would be awkward to not have this available in STASH.

We are currently using git flow from the commandline to create releases: merging a release branch into master and into development. Git flow creates a version tag in the process. The way stash allows us to creates branches and merges is very appealing, but not being able to tag is missing in this process.

It is related to STASH-3737

Thanks for the suggestion Brett. Could you add more detail around your workflow and when you would like to create the tag?