[HN Gopher] How to Scan Force Pushed Commits for Secrets
       ___________________________________________________________________
        
       How to Scan Force Pushed Commits for Secrets
        
       Author : mmcclure
       Score  : 15 points
       Date   : 2025-07-31 17:10 UTC (5 hours ago)
        
 (HTM) web link (trufflesecurity.com)
 (TXT) w3m dump (trufflesecurity.com)
        
       | orbisvicis wrote:
       | I believe git gc after force-push will remedy the situation by
       | deleting all unreachable objects, even circular references.
        
         | londons_explore wrote:
         | Locally yes, but not on GitHub.
        
       | londons_explore wrote:
       | I really don't see how GitHub can justify allowing public access
       | to dangling commits.
       | 
       | Surely they have a whole army of paying customers demanding
       | proper data deletion ability (required for all kinds of legal
       | reasons - eg. We accidentally committed code we don't have a
       | licence for, or PII of Europeans, etc).
       | 
       | A simple rule saying 'any commit which ever has a refcount of
       | zero will become forever inaccessible unless reuploaded' would do
       | the trick.
        
       ___________________________________________________________________
       (page generated 2025-07-31 23:01 UTC)