feat: Add CI templates for fluent-operator #248
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
|
please have a look. @zhu733756 |
zhu733756
changed the title
zhu733756
approved these changes
Mar 24, 2022
Thanks for the great contribution! |
|
Seems those yaml file's end need a blank line, and I forgot to add. |
No matter, you can implement it by git forced pushing. |
Signed-off-by: mango <xu.weiKyrie@foxmail.com> Add CI templates for fluentbit-operator Signed-off-by: mango <xu.weiKyrie@foxmail.com>
Done. |
benjaminhuo
approved these changes
Mar 24, 2022
|
@mangoGoForward This is a great supplement to the current workflow, thanks for the contribution! |
Merged
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.
Signed-off-by: mango xu.weiKyrie@foxmail.com
What this PR does / why we need it:
Add CI templates for fluentbit-operator.
Which issue(s) this PR fixes:
Fixes #207
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: