Automated backup/release V2 #661
Open
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
|
The cron job for the monthly snapshot/release works as it created a snapshot/release on the first of this month and can be found here https://github.com/FalsePhilosopher/Flipper/releases/tag/Snapshot-2025-06-01 |
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.
This time it uses github actions as I didn't know github had a free tier of 2,000 hours a month for their runners. So no external machines needed for this to create a snapshot of the repo including all of the submodules, then creates a release with said snapshot. The resulting tar.zst is 2.0GB, if you were to git clone --recursive the repo it's 6.9GB. A POC can be found on my fork in the actions tab and in the release section.