-
Notifications
You must be signed in to change notification settings - Fork 23
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
playwright pr comment #8370
playwright pr comment #8370
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8370 +/- ##
==========================================
+ Coverage 73.50% 73.51% +0.01%
==========================================
Files 1332 1332
Lines 41200 41200
Branches 7665 7665
==========================================
+ Hits 30284 30290 +6
+ Misses 10916 10910 -6 ☔ View full report in Codecov by Sentry. |
@@ -1,6 +1,6 @@ | |||
name: CI | |||
|
|||
on: push | |||
on: [push, pull_request] |
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.
The PR ID isn't available unless I include this pull_request trigger for the playwright summary. Though I'm a bit worried this may not work in a non-PR context
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.
This runs when we version main and when we cut release branches, neither of which are pull requests
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.
Copied convo from slack:
Eduardo
1:26 PM
Theoretically it should be fine to add the additional trigger pull_request since every kind of that event is also a push, right? Just with extra information
1:26
Though I did notice that pull_request will checkout the merged version of all the commits in the PR rather than the tip of the branch
Graham
1:27 PM
What happens when it's a push without a pull_request though?
1:28
Ex: https://github.com/pixiebrix/pixiebrix-extension/actions/runs/8837003915
Eduardo
1:29 PM
Theoretically it won't pass.
I can add a check for when not to run a step:
if: github.event_name != 'pull_request'
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.
It's not clear to me what was decided here - could you clarify @fungairino ? I do see the github.event_name != 'pull_request'
clause below.
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.
Approving to unblock, because it seems like the conversation about adding the pull_request
trigger is resolved?
No loom links were found in the first post. Please add one there if you'd like to it to appear on Slack. Do not edit this comment manually. |
What does this PR do?
Discussion
Checklist