This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
repository path per workspace #2
Open
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
StoreKey is currently a constant. This is based on assumption that if we have many workspaces, all their exports are located in one folder. It causes problems if we have multiple workspaces whose exports are stored in different repositories (or multiple projects with workspaces stored in different repositories). I propose updating the pertinent logic so that each workspace's repo path is stored separately. Another approach would be to have a path per project, not per workspace.
Applying this update means that Repo Sync configuration has to be performed again for all workspaces.