add CI script to automatically update a git tag #2530
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.
Currently, anyone who wants to consume ELI's data has to fetch the data directly from the main git branch (via github pages or github), since this repository does not do versioning.
This can be risky, and cause confusion when the CI is failing on the main branch (like what happened last week).
To give data consumers more certainty, this PR introduces a weekly cronjob which moves a git tag to the latest commit on the main branch, but only if the CI is passing.
This gives people the flexibility to consume data directly from the main branch, or from this git tag if you want to be more safe.
Tested in a fork of this repository (logs here)