Proposal: Build Caching for all versioned libraries

[AMDphreak]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Actions Cache

Discussion Details

See also: #190654

Currently, every Dlang, Rust, or C++ project on GitHub re-compiles the same common dependencies (e.g., vello, glfw, phobos) hundreds, thousands, or millions of times, based on how many projects use a library. Even with actions/cache, the cache is isolated per repository or organization.

GitHub should implement a Global, Distributed, Content-Addressable Cache at the runner level, similar in spirit as Unison lang.

*How it would work:

1. Deterministic Hashing: When a build tool (like dub or cargo) requests a dependency, GitHub's runner generates a cryptographically secure hash of the source code, the toolchain version, and the build flags.
2. Global Lookup: Before compiling, the runner checks a Global GitHub Artifact Store. If an identical artifact has already been compiled by any open-source project (or any project within the user's organization), the runner instantly pulls the pre-built binary instead of compiling.
3. Cross-Project Sharing: This would effectively eliminate "dependency debt" across the entire ecosystem. If a new version of a popular library is released, the first person to build it on GitHub Actions "gifts" that pre-built artifact to everyone else on the platform.

This is different from current caching!!!: Current caching is Manual and Isolated. This proposal is for a Passive and Shared infrastructure. It turns GitHub Actions into a giant, distributed Build Farm that never does the same work twice.

The fact that this has not been done already is incredible to me. You guys are so lacking in engineering mentality it is disgusting. You have AI to implement this in a literal day and you haven't made a single move to fix these outstanding issues.

If you guys don't implement this, you are liable for consequences, because you are intentionally crippling your product in order to charge money for build time on unnecessary items. I want to see this implemented within the next year or I will bring this matter to relevant authorities.

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