-
Notifications
You must be signed in to change notification settings - Fork 7.7k
fix(gh-workflow): skip comment when push directly #6179
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
Open
awxiaoxian2020
wants to merge
1
commit into
reactjs:main
Choose a base branch
from
awxiaoxian2020:workflow
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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 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.
I believe the core problem lies in the evaluation of these lines by GitHub's runner. If
github.event.workflow_run.event
is not even the right parameter (as you implied in another PR), then this job should never run. Nevertheless, it runs, meaning that the condition is always set to true somehow - just like here: actions/runner#1173. Presumably,${{
and}}
syntax along with block formatting sign>
result in the text, thus making it a truthy value.Did you try other variations of that condition without the block sign
>
and withevent_name
like this?P.S.
Regarding the PR itself, I think we still need the
if
success check for the entirecomment
job. Otherwise, the remainingComment
step is going to produce an error in casesteps.get-comment-body.outputs
is empty.P.P.S.
Also, I was thinking that ignoring the default branch for this workflow can serve as an additional precaution as well:
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.
I actually checked and this did the trick:
event
is the right property and the evaluation is indeed broken.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.
How do you check this?
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.
@alinkedd I remember
>
was used for multiline?also I checked what other option we have for multiline and ended up here https://github.com/orgs/community/discussions/25641#discussioncomment-3248571 if we try with
|
and everything works properly then the problem might be with>
only?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.
@awxiaoxian2020 I tried hypothesis with same condition in my test repo and it seemed to be right.
UPD
The fixes for workflows triggered by
workflow_run
work only if they are added to the default branch, so I could not tested them here with PR.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.
@harish-sethuraman
It seems, the problem is not about block signs (
|
,>
, etc), but rather about expression within${{
and}}
and some text around it (even if it's|
or>
). So today I rechecked this more readable version without expression and it works fine:And I updated my another PR #6651 which also contains some other fixes
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.
Fixes have been moved to #7667