feat(ci): add StackBlitz templates for e2e apps#540
Conversation
|
|
Warning Review limit reached
More reviews will be available in 55 minutes and 31 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. 📝 WalkthroughWalkthroughThe CI workflow's publish step was updated to include two additional arguments: Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
View your CI Pipeline Execution ↗ for commit 0ee0434
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
More templates
@forgerock/davinci-client
@forgerock/device-client
@forgerock/journey-client
@forgerock/oidc-client
@forgerock/protect
@forgerock/sdk-types
@forgerock/sdk-utilities
@forgerock/iframe-manager
@forgerock/sdk-logger
@forgerock/sdk-oidc
@forgerock/sdk-request-middleware
@forgerock/storage
commit: |
|
Deployed 0251698 to https://ForgeRock.github.io/ping-javascript-sdk/pr-540/025169868367180985668b88c0e05fdc1517189f branch gh-pages in ForgeRock/ping-javascript-sdk |
📦 Bundle Size Analysis📦 Bundle Size Analysis🚨 Significant Changes🔻 @forgerock/device-client - 0.0 KB (-10.0 KB, -100.0%) 📊 Minor Changes📉 @forgerock/device-client - 10.0 KB (-0.0 KB) ➖ No Changes➖ @forgerock/oidc-client - 35.2 KB 14 packages analyzed • Baseline from latest Legend🆕 New package ℹ️ How bundle sizes are calculated
🔄 Updated automatically on each push to this PR |
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (21.97%) is below the target coverage (40.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #540 +/- ##
==========================================
+ Coverage 18.07% 21.97% +3.89%
==========================================
Files 155 157 +2
Lines 24398 25188 +790
Branches 1203 1474 +271
==========================================
+ Hits 4410 5534 +1124
+ Misses 19988 19654 -334 🚀 New features to boost your workflow:
|
|
How are the templates useful? Is the idea so that we can copy paste the package.json into our e2e locally so we can run the test suites? Also, the templates generated by Stackblitz don't seem to boot up the application in the browser. There might be some error I'm not seeing. |
ryanbas21
force-pushed
the
feat/stackblitz-templates
branch
from
5615d50 to
f528f61
Compare
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
We determined these e2e failures are unrelated to this PR's changes, which only affect CI publishing configuration. The same failures are reproducible in branch 576, confirming a pre-existing issue with the external PingAM/ForgeRock OAuth2 service returning invalid_request errors for all authentication flows. The affected projects (@forgerock/protect-suites, @forgerock/oidc-suites) were not touched by this PR.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
ryanbas21
force-pushed
the
feat/stackblitz-templates
branch
from
f528f61 to
33d5a85
Compare
ryanbas21
force-pushed
the
feat/stackblitz-templates
branch
2 times, most recently
from
e2cb9cc to
60a7d52
Compare
Adds --template flag to pkg-pr-new so PR comments include interactive StackBlitz links for all e2e apps. Also switches to --pnpm for correct packing in the monorepo.
ryanbas21
force-pushed
the
feat/stackblitz-templates
branch
from
60a7d52 to
0ee0434
Compare
3 participants
Summary
--template './e2e/*-app'topkg-pr-newso PR comments include interactive StackBlitz links for all e2e apps (davinci, journey, oidc, device-client, protect)--pnpmflag for correctpnpm packbehavior in the monorepo--packageManager=pnpmso PR comments showpnpm addinstall commandsTest plan
pnpm packis used (check CI logs for pack output)Summary by CodeRabbit