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

Community Notes

Thanks to all who have shared their interest and support so far!

If you want to voice your support for this topic, please upvote it by clicking the upvote arrow ⬆️ to raise awareness and help GitHub prioritize this request.

Please avoid leaving "+1" or "me too" comments; they generate extra noise for discussion followers and do not help prioritize the request.

[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.

[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

[taranarmo]

They have it in Desktop version but not on web version

It's funny considering that desktop is an Electron app (at least it's in JS/TS)

[Polkas]

+1

[JoeCap08055]

+1

[Zzhiter]

+1

[narendral590]

+1

[Bingmang]

plz +1

[akademy]

+1

Just needed this today. Seems odd not being able to do is.
(Having said that, GitHubs UIs are terrible, maybe it's available somewhere I can't find...)

[spenserblack]

I hope if this is implemented that it will sign tags, so that tags made from the web UI will be verified. Creating releases currently doesn't do this, and AFAIK the only way to create a signed/verified tag is to create it from the CLI and push it.

[Daniele71]

+1 Please !

[CPG-Philips]

+1

[eamreyes]

+1

Yet another missing feature in GH. My dissappointment is immesurable and my day is ruined.

[srendarevskii]

+1

[syedahmedx3]

It’s a bit frustrating that the UI lets us 'Search or create' branches, but tags still lack that functionality.
Not every tag needs to be a full 'Release.'
Sometimes we need to mark a stable commit or an architectural milestone without the extra noise.
Relying on the CLI isn't always possible when you're on a mobile device or conducting a quick audit.
Adding a native 'Create Tag' button would be a huge improvement for a clean, efficient workflow.

[arthur-carpentier]

+1

[mste-milestonedk]

3 years and still nothing?

[CSharpino]

+1

[wl-spaceline]

+1
Annoying that such a basic feature has not taken into consideration in more than 2 years

[SergioB-dev]

This would be a great addition.

[Peneheals]

How is this function still missing? Pathetic... Meanwhile the community codebase is freely used to train AI...

[domino-pl]

+1

[sethjackson]

We are currently missing this workflow at $WORK and it’s quite a pain that it is missing. It is present in other SCM hosting platforms but still missing after all these years in GitHub.

For our use case we use tags in our Jenkins shared library repositories to denote what is current in the shared library. This allows us to quickly roll forwards or backwards without too much hassle if something is broken or needs updating as we can just commit and move the tag around. We could do this in the UI of the previous SCM platform we used but we can no longer do this in GitHub UI.