Cloning the Repo onto the VM and clean-up #11
Merged
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
…ository. So not to clone all the other repo files
… for previous backlog tasks not in action this trimester
ben-AI-cybersec
approved these changes
Sep 4, 2024
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.
Data warehouse needs to be able to commit work from the VM. I have cloned the repo to the VM but only in my 'data-lakehouse' folder. From here I have moved obsolete code into 'Archive' and shuffled the folders into more logical groups, rearranged some files currently in use.
The Data Warehouse team and I up until now haven't been pushing the code up from the VM to git so I expect there will be more PR like this to come when they move their git repos from PC to VM.