`validate_jinja` action will fail with "bad revision" sometimes.

[BryceStevenWilley]

GITHUB_SHA will not always be the correct HEAD value of the repo, for unintuitive reasons. If we get errors like fatal: bad revision from git, we should just check all of the docx's, instead of trying to get just those that changed recently.

• Relevant line in ALActions
• Where the script fails

Should just run find . -name "*.docx" if git fails for any reason.

The details about how GitHub handles SHAs for certain force pushes here:

https://github.com/orgs/community/discussions/26325

[BryceStevenWilley]

7b013e6 seems to work (proof at: https://github.com/SuffolkLITLab/docassemble-EFSPIntegration/actions/runs/19582337504/job/56083412682, at least enough for it to stop failing when it shouldn't at all. More tests probably needed to make sure it does find docxs when they exist, I'll see if it works for an AssemblyLine branch at some point.