[Phase 7] Soft-launch E2E PR checks#364
Draft
kieran-osgood-shopify wants to merge 1 commit into
Draft
Conversation
This was referenced Jun 29, 2026
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
33b81d9 to
dc1c907
Compare
6a6674a to
548ffe1
Compare
ea86286 to
e791f00
Compare
1f81b20 to
c346dc8
Compare
e791f00 to
3545355
Compare
c346dc8 to
c0cb990
Compare
9bcd74d to
64cf7a4
Compare
261b9df to
8cea139
Compare
3895dbe to
9a25f02
Compare
3baf4b0 to
f219a0f
Compare
9a25f02 to
8477810
Compare
f219a0f to
9112818
Compare
8477810 to
3399b8d
Compare
9112818 to
efb1d4f
Compare
f29c0b4 to
a9a9150
Compare
f6f41e8 to
d2ae60d
Compare
a9a9150 to
5cbc8cf
Compare
5b48786 to
7942882
Compare
5cbc8cf to
219ee3f
Compare
7942882 to
7d6f887
Compare
219ee3f to
165945b
Compare
7d6f887 to
06005bc
Compare
165945b to
98c8a2e
Compare
11 tasks
|
🤖 Bitrise Build Report > Checkout Kit E2E > e2e > #55: ✅ SUCCESS
|
98c8a2e to
8ce0b60
Compare
8e949ef to
df9ceff
Compare
8ce0b60 to
7e62db6
Compare
Contributor
Author
|
^I have disabled these bitrise build report comments so its only the one we manually post above in future |
7e62db6 to
f214365
Compare
df9ceff to
d2d5b3e
Compare
f214365 to
8570f64
Compare
3d9c51f to
ced0bde
Compare
9d963fc to
bf49ea7
Compare
This was referenced Jul 7, 2026
Assisted-By: devx/6c1e3ad5-96c8-4972-b087-da7ff7b195c3
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Stack Context
This is Phase 7 of the BrowserStack Maestro E2E stack for Checkout Kit, stacked on GitHub E2E reporting.
Parent issue: https://github.com/shop/issues-checkout-kit/issues/1101
Epic: https://github.com/shop/issues-checkout-kit/issues/1084
What?
This PR adds the "pull_request" trigger to the bitrise config, launching the e2e pipeline when a PR is created
Skips draft PR's
E2E_STRICT=falsemeans the failures are soft failures, when we're certain the pipeline is stable we can setE2E_STRICT=true, keeps assertion failures reportable without blocking initial PR progress(Technically even without E2E_STRICT they wouldn't be blocking because we havent marked the bitrise status checks as required, however it gives us an opt out in future too)
Why?
The E2E pipeline should start non-blocking while the infrastructure and suite stabilize. Developers still get commit statuses, Check Runs, and actionable failure comments, but PR progress is not blocked until we are confident that the checks are free of false positives
Results
Topology on Bitrise

When one suite is failing

After fixing all the tests you'll see the workflow update the comment