Update repos used in deployments #645
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
This commit updates how repositories are used within deployments. Previously, when creating a deployment, Ramble would create configuration files to add the deployment into the resulting workspace. This commit changes this behavior so that the repository is created, but it is added at deployment pull time instead of deployment push time. This allows the path of the deployment respository to be absolute on the remote machine rather than a relative path that hopefully will work on the remote machine.
linsword13
reviewed
Sep 13, 2024
linsword13
approved these changes
Sep 13, 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.
This merge updates how repositories are used within deployments.
Previously, when creating a deployment, Ramble would create configuration files to add the deployment into the resulting workspace.
This merge changes this behavior so that the repository is created, but it is added at deployment pull time instead of deployment push time. This allows the path of the deployment respository to be absolute on the remote machine rather than a relative path that hopefully will work on the remote machine.