Open
Conversation
Member
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.
Description
I set up a local repository for SwellStaticFiles using
git-annex. This works by storing files in anannexlocation and having git only manage symlinks to those files, updating the links whenever changes are made. This makes for a more lightweight process. We can keep this as a local repository for now, but we can eventually add remotes such as s3 or other backup locations. I propose to pin versions of those files to worktrees in the static files location (for example, I called the preliminary versions v0.0.0). We can make changes in thedevelopversion, then create a tag and new worktree when we want to switch versions. These files are identical to the ones Swell has been using up until now so there's zero diff, I did add a basic readme briefly explaininggit-annexin the repository.