Use git pull --rebase before attempting git push #86
Conversation
This file contains 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
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Should address #53 (comment).
Discussed in https://epiforecasts.io/posts/2022-04-11-robust-actions/#git-repository-out-of-sync.
It took me a while to implement this as I was unsure about whether it could lead to out-of-sync snapshots in history. After staring at the code & GHA logs for a while today, I don't think it's an issue as the time in the csv file name is saved right after we do the CRAN snapshot.
If workflows take a while to get started, to install packages, etc., and snapshots are uploaded out of order, it shouldn't matter because the recorded time is still correct.