Nice write up and 'how to' guide. I am going to implement this in our organisation. All private repos here, but we once had some inadvertently commit a develo

Nice write up and 'how to' guide. I am going to implement this in our organisation. All private repos here, but we once had some inadvertently commit a development '.env' file with credentials in it to our remote Git repo (they did it before we added '.env*' to our .gitignore file). We might start peppering our .env files with honeypot keys just to track if they have somehow been compromised outside the company.