Create tag in UI without creating release

[merusso]

Select Topic Area

Product Feedback

Body

As a user, I would like to create a Git tag from the repository browser UI without having to create a release.

When creating a tag, I'd like to be able to specify a branch or commit hash as a target for the tag.

This is pretty basic functionality that is available in most other source code management tools. For example:

• Bitbucket: https://support.atlassian.com/bitbucket-cloud/docs/repository-tags/
• GitLab: https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-tag

[aaron-oxford]

Me too!

[RealDoigt]

I'd love this so much

[hatamiarash7]

For example, i need to create tag and create a release automatically using goreleaser... I can't do this in browser.

[nywilken]

Not the solution we’re looking for but a workaround in this case is to use the draft new release to create the tag on publish.

1. Enter tag name to create on publish, with the required tag target
2. Publish release as pre-release
3. Immediately delete the release.

The tag remains in place and let goreleaser run as expected.

The caveat is that you may get two release notifications.

[jannes-io]

PHP composer/packagist works based on git tags, not having to create a GH release but still being able to push a new version/hotfix of a package without needing a local version of the repository would be brilliant... It's the one feature I'm really missing from BitBucket.

[brettwgh]

yes please

[marcusmendes-dev]

please +1

[GuyWhoKnowsTheGuy]

please +1

[vamseeganti]

[jannes-io]

You may have misread the topic. What you’re suggesting is the opposite of the original post. We’d like to tag a commit from the UI, essentially just running “git tag -a …” on the selected commit. Not start a branch from a tag? 🤨

[vamseeganti]

Agreed

[bminghelli]

+1

[orenault]

+1

[bish0polis]

day 575 . Any word?

[dmknght]

day 575 . Any word?

They have it in Desktop version but not on web version. IDK why
https://docs.github.com/en/desktop/managing-commits/managing-tags-in-github-desktop

[Polkas]

+1

[JoeCap08055]

+1

[Zzhiter]

+1

[narendral590]

+1

[Bingmang]

plz +1

[bmiller-0]

+1

[hollstein]

+1

[katbyte]

+1

[PhilJahn]

+1

[egvijayanand]

Basic feature, definitely +1

[Quinhas]

+1

[asaharn]

+1

[Losenmann]

+1

[sjaeger92]

+1

[nr-aplazo]

+1

[davidwtucker]

+1

[hayk96]

+1

[ridhoperdana]

+1

[Danielseta]

The ability to create Git tags directly from a repository browser UI, without the requirement of creating a full release, is a fundamental and expected feature for many developers. This functionality, readily available in platforms like Bitbucket and GitLab, streamlines common tagging workflows. Forcing release creation for simple tags adds unnecessary complexity, as tags are frequently used for lightweight versioning, marking specific commits (like hotfixes), or bookmarking key points in project history. Crucially, flexibility in targeting either a branch or a specific commit hash is essential, accommodating scenarios where tagging the tip of a branch isn't desired. A web UI should ideally mirror Git's core capabilities, allowing tagging of any commit, consistent with the command-line interface. A simplified tagging process enhances the developer experience, reducing friction and enabling focus on core tasks. Furthermore, separating tag creation from release management improves accessibility, empowering a broader range of team members, such as testers and documentation writers, to contribute to versioning.