💬 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. ⭐

Select Topic Area

Bug

Body

For many years I've been tracking https://github.com/orgs/community/discussions/6003. Being unable to disable this has been annoying for many years, and this effects both enterprise and community.

On the community side, you often don't want the users using a git-archive tarball - this is kinda madness for most modern dev environments where you really want users to install from your languages package repository.

On the enterprise side, you almost never want this!

I understand that there's some concern that removing this could effect older parts of the github code base. The fix would really be to just disable showing those links in /releases via a config option.

Please someone take this up!!!!

This should be an easy fix. There's already an ability to edit a release to add detailed notes and modify meta data. There needs to be a checkbox that allows the show/hide of the default source zip files.

Given that GitHub actively promotes things such as Issues Only Repositories where having asset downloads make zero sense, this seems like it should be a priority.

Like many repos, we have a workflow that produces semantic releases of a package that only contains part of the repo as a deliverable for end users. They don't need the zip / tarball of the whole repo. Those that want to actually delve into the repo and contribute can fork and pull, and they do.

Fully agree, especially as one common workaround seems to be to change the .gitattributes in order to exclude the code from being archived. Unfortunately this conflicts with the way how github uses actions, if consumed from such a repository which modified its .gitattributes in that way.

My use case is having a private repository for my application's source code, but I need to distribute binaries (release executables) to users via a public repository. The existence of the mandatory "Source code (zip/tar.gz)" links on GitHub releases is a blocker for me, as I do not want to make my source code public, only the release artifacts.

Just like others here, I would highly appreciate an option to disable or hide the source code links in releases. This would let me (and many others) use GitHub Releases for distributing binaries without exposing the code itself. Please consider prioritizing this feature!