Feat/linux support - #11
Merged
Merged
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.
Implemented
Verified
We also put back git worktree support. The original intent was "why is a worktree needed for this?" and the reason is the purpose of the git worktree was to omit things that weren't necasasry for the sandbox like build images and such, which resulted in a smaller snapshot.
The Git-aware snapshot included:
This produced a smaller, safer, project-focused snapshot. Git also provided a stable baseline for tracking guest changes and exporting patches.
Removing git worktree support caused a major regression where effectively, all of the files within a directory where you started
aboxwould be within the snapshot, causing major increases in storage.