Workflow to build specific PRs for autodeployment #114
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
Signed-off-by: Marco A. Gutierrez <marcogg@marcogg.com>
Signed-off-by: Marco A. Gutierrez <marcogg@marcogg.com>
norbusan
approved these changes
May 24, 2024
|
I actually thought this through and I will make this deploy directly to development, no point on having two dev servers. |
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.
Adding a workflow that helps build PRs from any repo and reference declared on the input and pushes them to
eventyay/eventyay-ticketswith the tagpr-deploymentso we can auto deploy them in the test server that has been recently created and check the result before merging.