ci: scripts to redeploy in developments #65
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
froger
force-pushed
the
ci/testing-pipelines
branch
10 times, most recently
from
9650998
to
4826638
Compare
froger
force-pushed
the
ci/testing-pipelines
branch
from
4826638
to
c18abf3
Compare
|
@RCheesley the redeploy workflow has been tested here: https://github.com/octree-gva/community.mautic/actions/workflows/redeploy-dev.yml And it works: => I will bypass branch protection to move forward with action setup and having something functional, as it blocks all the other issues |
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 PR add a workflow to redeploy an environment to a specific tag. This will allow us to have a manual action to redeploy testing environment and/or production when you want.