If you’re reading this thinking “ why would someone tag a commit from the UI? The command line works just fine for me.” Lets look at where you can save time and find commits that need tagging in Bitbucket without switching over to the command line: The name of the tag, date/time, and author can be applied to any commit. Add tags from the UI vs the command lineīitbucket users have asked us how they can cut out this back and forth and tag commits directly from Bitbucket Cloud’s UI, and today we’re launching this capability to add annotated git tags and regular mercurial tags directly to commits from the UI. This is a major pain (shakes fist at context switching).

You find the commit and realize that it is missing a release tag, so you go to the command line – create and push the tag so you can tag the commit for the release, then go back to Bitbucket’s UI to view the tag and ultimately, do the release. Here’s a look at a hypothetical scenario for adding tags: You’re a release manager getting ready for a release so you navigate to Bitbucket’s UI and view all the commits, looking for the one that has all the features you want to include and has passing builds. If you change versions a lot, they are a life saver for an organization instead of just using branches, which commonly leaves you with lots of rarely used branches.

They reduce complexity, clean up your branch workflow, and are a way to mark exact versions of commits. Git tags have become essential to a Git workflow to mark specific points in your Git history (like referencing a specific version of a project by tagging a commit for your release).

Add ta tag metadoctor