Red Hat Konflux update openperouter-operator-fbc-4-20 #3
Conversation
This file contains hidden or 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
oribon
force-pushed
the
konflux-openperouter-operator-fbc-4-20
branch
22 times, most recently
from
8d6a3b3 to
6738eed
Compare
oribon
force-pushed
the
konflux-openperouter-operator-fbc-4-20
branch
8 times, most recently
from
9033db2 to
92b40eb
Compare
oribon
force-pushed
the
konflux-openperouter-operator-fbc-4-20
branch
2 times, most recently
from
0b8d8e5 to
537f032
Compare
Signed-off-by: red-hat-konflux <[email protected]>
Signed-off-by: Ori Braunshtein <[email protected]>
oribon
force-pushed
the
konflux-openperouter-operator-fbc-4-20
branch
from
537f032 to
5984ef2
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.
Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content
/ok-to-testFor more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization
Please follow the block sequence indentation style introduced by the proprosed PipelineRuns YAMLs, or keep using consistent indentation level through your customized PipelineRuns. When different levels are mixed, it will be changed to the proposed style.