This repository was archived by the owner on Jun 30, 2025. It is now read-only.
fix: fail immediately if no commit timestamp found for push event #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
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
|
ReenigneArcher
force-pushed
the
fix-ensure-correct-operation-on-push-events
branch
2 times, most recently
from
cf9e544 to
fbba7e3
Compare
ReenigneArcher
force-pushed
the
fix-ensure-correct-operation-on-push-events
branch
from
fbba7e3 to
24a9578
Compare
ReenigneArcher
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
.github/...)Checklist
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.