If you find a .secrets file in Git history, changing the key is mandatory. If you cannot change the key (e.g., a hardcoded SSL private key), you must use git filter-branch or BFG Repo-Cleaner to purge it from existence.
Warning: Rewriting history breaks forks and PRs. Do this only during a scheduled maintenance window. .secrets
If you must keep a .secrets file for local development, encrypt it. If you find a
If you shouldn't use a plaintext .secrets file, what should you do? You must adopt Secret Management Tooling. Here is how professionals handle the keyword .secrets without the risk. If you must keep a