Add *hashed* file version to .gitallowed? So future changes get caught containing secrets again about git-secrets HOT 1 OPEN

It sounds like a reasonable enhancement to git-secrets to provide a more granular and secure way of handling exceptions using hash-based whitelisting. This could be particularly useful in situations like yours where the content of the files may change, but you want to ensure that the specific versions you've approved are the ones being tracked.

Before proceeding with a pull request (PR), I would recommend discussing the idea with the maintainers of the git-secrets project. They may have valuable insights and feedback on the proposed feature, and it's always a good practice to get their buy-in before investing time in the development.

You can open an issue on the git-secrets repository to initiate a discussion about this potential enhancement. Clearly outline the problem you're trying to solve, propose the solution with hash-based whitelisting, and explain how it could benefit the community. If the maintainers are receptive to the idea, they may guide you on the best way to implement it or even invite you to submit a PR.

Remember to check the project's contribution guidelines and coding standards before submitting a PR, and make sure to test your changes thoroughly to ensure they integrate well with the existing functionality.

from git-secrets.