Tags events notifications in watching settings

[darkred]

Currently, for repos, in the relevant: 'Watch' | 'Custom' dropbown, there's a Releases option. My suggestion is to add another option, Tags, to be able to get notifications for new tags, even if there hasn't been created a relevant release from it. Here is a mockup:

Example repo: https://github.com/Lexikos/AutoHotkey_L/releases where the last release is from May 8, but there have also been 6 new tags since then:

[jab]

Just want to add that a lot of GitHub projects that make releases to the standard, public package registries for their language (e.g. PyPI, npm registry, etc.) don’t ever create corresponding GitHub releases, but do push corresponding git tags to GitHub. So the GitHub users who are intending to watch such projects for new releases don’t actually ever get notified about the new releases, which they may only find out about after it’s too late to avoiding missing an important release.

Could the GitHub team please comment on whether an additional “Tags” option could be added to the choices in the “Custom” menu?

[h-vetinari]

xref dear-github/dear-github#399

[andry81]

Just wanted to inform, there is not enough to track only the releases or tags creation. Needs to track assets update in each or last release, because assets can be updated separately.

[h-vetinari]

That's a related but separate issue. Many problems would be solved already by being able to track tags, without having anything to do with assets uploaded to a release. In fact tracking tags is most interesting for projects that don't use the release functionality (and therefore don't attach any assets at all anyway).

You should open a separate issue for this.

[andry81]

If you rely only on tags or releases creation then, you can lose the moment when a repo author would stop add tags/releases and start to update only assets + release readme.

[h-vetinari]

I understand. Still unrelated to projects that keep publishing tags and only tags, of which there is a substantial number.

A lot of the time that is because GitHub is only a mirror for an upstream git remote, so the chances that such a repo will switch to only assets are miniscule.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐