-
Notifications
You must be signed in to change notification settings - Fork 123
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
Update ABI Diff Action to work correctly on push events #2188
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2188 +/- ##
==========================================
- Coverage 79.04% 79.03% -0.01%
==========================================
Files 612 612
Lines 106064 106064
Branches 14994 14995 +1
==========================================
- Hits 83833 83825 -8
- Misses 21579 21587 +8
Partials 652 652 ☔ View full report in Codecov by Sentry. |
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.
Looks fine but in the context of AWS-LC, what is considered a push event?
We usually merge stuff in through PR's right (which I guess the second part of these statements covers?)
@@ -19,12 +19,12 @@ jobs: | |||
- uses: actions/checkout@v3 | |||
with: | |||
repository: aws/aws-lc | |||
ref: ${{ github.ref }} | |||
ref: ${{ github.event_name == 'push' && github.event.ref || github.event.pull_request.head.sha }} |
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.
NP: Are parenthesis needed here and below?
ref: ${{ (github.event_name == 'push' && github.event.ref) || github.event.pull_request.head.sha }}
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.
GitHub doesn't seem to outright state precedence order for evaluation, but it appears to be left-to-right. See the example here that is basically the same as the line I have: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#example
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.