fix: fail immediately if no commit timestamp found for push event

[ReenigneArcher]

Description

After merging #107 this no longer runs properly on push events. This PR probably doesn't actually solve the problem, but adds some debugging prints to the workflow to help investigate the issue further.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.67%. Comparing base (fc138bd) to head (24a9578).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #108      +/-   ##
==========================================
- Coverage   98.69%   98.67%   -0.02%     
==========================================
  Files           1        1              
  Lines         153      151       -2     
==========================================
- Hits          151      149       -2     
  Misses          2        2              

Files	Coverage Δ
action/main.py	98.67% <100.00%> (-0.02%)	⬇️