Add trigger-private-ci.yaml #2845
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
| types: [created, edited] | ||
| pull_request_target: | ||
| types: [opened, reopened, synchronize] | ||
| branches: [ros2-development] |
There was a problem hiding this comment.
replace this to "ros2-hkr"
There was a problem hiding this comment.
do you mean you want different ci processes for different branches, or do you want 2 kinds of ci to work for every PR?
There was a problem hiding this comment.
for ros2-development, keep the same behavior (3 scripts inside .workflow - main_ci, cppchecker, prerelase)
for ros2-hkr, we will have cppcheck and your new script.
timor-raiman
force-pushed
the
timor-trigger-private-ci
branch
from
be47dd2
to
3b7ab9b
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.
No description provided.