Staging/test branches #2
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
cds88
force-pushed
the
staging/test-branches
branch
2 times, most recently
from
55078b0 to
32faa4f
Compare
cds88
force-pushed
the
staging/test-branches
branch
from
32faa4f to
a835219
Compare
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.
Implement extra staging multi branch environment.
Configuration allows developers to create staging branches with distinct names which correspond
to isolated contenerized environments on the remote server.
A git push to staging/test-branches create a
test-branchessubdomain with entire isolated environment.This allow developers utilize staging environments to the core without colliding with each other.