-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test conditional tests #1052
Merged
Merged
test conditional tests #1052
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
comment |
test |
test |
run |
a |
aaaa |
/deploy |
Derstilon
approved these changes
Jun 1, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try it
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 dev-ops PR introduces two new testing pipelines intended to be triggered on demand.
The idea is not to run long running tests and deployment after every commit.
This PR introduces new feature. If on a PR discussion a comment appears with
/test
then a test suite defined in https://github.com/yaptide/ui/pull/1052/files#diff-cb08d37d26dd2d11ba4235a4aff4a4fb8c49779b0f9b5c3884531244d2566d5a will be scheduled for execution.In a similar way PR comment with
/deploy
will trigger deployment of docker image to GHCR.This functionality could be tested only after merge, issuing any
/test
or/deploy
comments in this PR won't have any effect.The plan for the future:
/test
and/deploy
triggered) and automated (after every commit) builds for a while to properly test bothI was heavily inspired by:
https://dev.to/zirkelc/trigger-github-workflow-for-comment-on-pull-request-45l2