title: Managing Rails Precompiled Asset Bloat Between Git/GitHub and Heroku
body: <p>It seems that most stack overflow posts recommend precompiling Rails assets before deploying on Heroku to avoid compilation errors and to ensure a fast deploy. However, what is common-practice on managing a long-lived repo with tons of asset bloat in Git/GitHub? I have a repo with a couple years of commits and a couple GB of git data interleaved with "precompiling assets" commits, which I feel like must not be the best-practice for this. Anyone have recommendation for cleaner way to manage the sync between GitHub and Heroku repos without polluting Git history with a ton of large ugl(ified)y files? I periodically clean the old assets but this doesn't help with managing the repo size unless I kill/squash my history, which I'd prefer not to do.</p>