Add attribute-based filters to GitHub Release assets #213560
Replies: 3 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
The problem is real — 30 assets with four independent attributes is a lot of filename decoding — but there's a structural reason this is hard to fix purely in the UI. Release assets don't have typed fields. To GitHub, What works today:
If you want to push the platform direction, I'd narrow the ask: rather than "filters for architectures and variants", propose structured metadata on release assets (a small key/value map or a manifest file) plus a minimal UI that filters on it. That gives maintainers a way to declare the attributes once, and the UI can stay generic. Otherwise you're asking GitHub to hard-code Notepad++'s naming rules. |
|
Welcome to the GitHub Community, @kakogawa! You are more likely to get a useful response if you are posting your question in the applicable category and are explicit about what your project entails--giving a few more details might help someone give you a nudge in the right direction. I've gone ahead and moved it for you. Good luck! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Other
Body
Problem
GitHub Releases currently display all downloadable assets in a single flat list, regardless of their purpose or characteristics.
For projects that distribute software across multiple architectures and packaging formats, the number of files can grow significantly because several independent attributes are combined.
For example, a single release of Notepad++ 8.9.9.1 contains approximately 30 downloadable entries, including:
.sigsignaturesSome example filenames:
As more combinations are added, the asset list becomes increasingly difficult to navigate.
Users have to inspect filenames individually to determine which file matches their requirements. This is particularly inconvenient for users who simply want to download the correct installer or portable package for their system.
Current Behavior
All release assets are displayed together in one unfiltered list.
The only way to distinguish these files is to understand their naming conventions and manually inspect each filename.
Proposed Improvement
Introduce attribute-based filters for the asset list within each individual release.
Users should be able to combine multiple filters to narrow down the results.
Suggested filter categories:
1. Package Type
2. Architecture
3. Variant
4. File Format
5. Signature Files
.sigfilesThe available filter options should reflect the assets actually present in the release.
Current vs. Proposed Experience
Current experience:
Users see every file at once, including all combinations of architectures, package types, variants, formats, and their associated signature files.
For example, finding the ARM64 portable package requires manually scanning filenames such as:
Proposed experience:
A user could select:
The result would be reduced to:
Instead of manually examining dozens of entries, users could find the exact file they need through a few filter selections.
Implementation Considerations
Ideally, GitHub could provide structured metadata for release assets, allowing maintainers to specify attributes such as architecture, package type, and variant.
Where possible, GitHub could also automatically recognize common filename patterns to reduce the amount of manual work required from maintainers.
The existing unfiltered asset list should remain available when no filters are selected, preserving the current experience for projects with only a few assets.
Benefits
Related Discussion
There is an existing discussion about faceted search for releases, including filtering by attached asset name, file type, and size:
https://github.com/orgs/community/discussions/6006
However, this proposal focuses specifically on filtering the asset list within an individual release, using meaningful attributes such as package type, architecture, variant, and file format.
I believe this would be a valuable usability improvement for both software maintainers and users who download software from GitHub Releases.
All reactions