We need to look into handling a large number of files as we currently have errors due to wrong commit SHA being used when we update multiple files (missing await somewhere).

We also will hit API limits as well because we are creating a new commit per file. We should look into using bulk commits, maybe using the git data API.

Action doesn't seem to handle committing removed files well.

Example: https://github.com/getsentry/security-as-code/actions/runs/6302004945/job/17108284070#logs

Error: Error: ENOENT: no such file or directory, open '/filename'
    at Object.openSync (node:fs:590:3)
    at Object.readFileSync (node:fs:458:35)
    at /home/runner/work/_actions/getsentry/action-github-commit/v1.1.0/dist/index.js:92:50
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/getsentry/action-github-commit/v1.1.0/dist/index.js:35:58)
Error: ENOENT: no such file or directory, open '/filename'

There are actions in the marketplace that solve the same problem, we should use one of those rather than maintaining our own.

https://www.google.com/search?q=action+github+commit

https://github.com/marketplace/actions/add-commit
https://github.com/marketplace/actions/git-auto-commit
https://github.com/marketplace/actions/github-commit-push
https://github.com/marketplace/actions/github-action-for-committing-changes-to-a-repository
https://github.com/marketplace/actions/verified-commit

@asottile further suggests that we could reimplement with pre-commit ci or pre-commit ci lite which handles this in a safe manner without exposing creds to GHA.