Add support for status_file in put #278
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
There are two ways of providing comments to the put step:
commentandcomment_file. The first one can be used for hard-coded comments while the later can be used for dynamically generated comments.Dynamically generating the status is not possible. It can only be set via the
statusoption.Similar to the
comment_filethis PR adds anstatus_fileoption.Use case: I execute unit-tests in the PR validation. If the creator of the PR made a mistake and therefore made the unit-tests fail, I don't want to have a red pipeline. For me, as a maintainer of the pipeline, everything works as intended. A red pipeline should indicate "something went wrong" (timeouts, missing permission to access GitHub, etc.), but actually the validation successfully detected a problem in the PR and successfully reported this back to GitHub.