Make S3 backups bare #316
Merged
Make S3 backups bare #316
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
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.
Every other destination is Git-based, meaning pushing all refs (which is what's happening) will ensure all remote branches are copied and backed up.
For the S3 destination, this is not the case since the repo is pushed as-is. This means an S3 backup will only have the default branch checked out. This is fixed by backing up a bare clone.
Maybe add to the S3-dest docs that you can restore a bare clone into a normal Git repo with
git clone /path/to/bare /path/to/normal?