-
Notifications
You must be signed in to change notification settings - Fork 40
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
chore: update pr workflow #615
Conversation
1990fb6
to
fb8a396
Compare
Codecov Report
@@ Coverage Diff @@
## main #615 +/- ##
=======================================
Coverage 67.01% 67.01%
=======================================
Files 129 129
Lines 5990 5990
Branches 1140 1140
=======================================
Hits 4014 4014
Misses 1606 1606
Partials 370 370
Flags with carried forward coverage won't be shown. Click here to find out more. 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Asset Size ReportMerging this pull request will result in the following CDN asset size changes:
Merging this pull request will result in the following NPM package consumer size changes:
Other Standard CDN AssetsReleased Assets
Built Assets
Other Polyfill CDN AssetsReleased Assets
Built Assets
|
fb8a396
to
9a554a1
Compare
9a554a1
to
d1fc8da
Compare
a50ac82
to
d0a98ec
Compare
d0a98ec
to
93ec48c
Compare
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.
Nice job with this! -- Approved, just don't forget to update the PR description
Workflow updates to provide faster feedback on pull requests, cleanup nightly jobs, and make re-usable workflows for jil testing.
Overview
Workflow updates:
pull_request
event. The remaining jobs will run on manual dispatch.WDIO Coverage
andWDIO
jobs so they run in parallel. Keeping the wdio coverage execution in a separate job so it runs fast and isolated.JIL: Single Browser
for each browser and collection (unit, functional).main
, only the workflow start for the last merge will finish executing. All others will be cancelled.Related Issue(s)
https://issues.newrelic.com/browse/NR-137546
Testing
N/A