[Phase 7] Soft-launch E2E PR checks - #364
Merged
kieran-osgood-shopify merged 1 commit intoJul 15, 2026
Merged
Conversation
This was referenced Jun 29, 2026
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
from
June 29, 2026 16:04
33b81d9 to
dc1c907
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
2 times, most recently
from
June 29, 2026 16:38
6a6674a to
548ffe1
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
2 times, most recently
from
June 29, 2026 17:01
ea86286 to
e791f00
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
3 times, most recently
from
June 29, 2026 17:33
1f81b20 to
c346dc8
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
from
June 29, 2026 17:33
e791f00 to
3545355
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
June 29, 2026 17:53
c346dc8 to
c0cb990
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
2 times, most recently
from
July 1, 2026 09:54
9bcd74d to
64cf7a4
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
2 times, most recently
from
July 1, 2026 10:07
261b9df to
8cea139
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
2 times, most recently
from
July 1, 2026 10:40
3895dbe to
9a25f02
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
2 times, most recently
from
July 1, 2026 11:26
3baf4b0 to
f219a0f
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
from
July 1, 2026 11:26
9a25f02 to
8477810
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
July 1, 2026 11:43
f219a0f to
9112818
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
from
July 1, 2026 11:43
8477810 to
3399b8d
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
July 1, 2026 13:41
9112818 to
efb1d4f
Compare
11 tasks
|
🤖 Bitrise Build Report > Checkout Kit E2E > e2e > #55: ✅ SUCCESS
|
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
July 6, 2026 08:33
98c8a2e to
8ce0b60
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
2 times, most recently
from
July 6, 2026 11:18
8e949ef to
df9ceff
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
July 6, 2026 11:18
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 |
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
July 6, 2026 12:33
7e62db6 to
f214365
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
from
July 6, 2026 12:33
df9ceff to
d2d5b3e
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
from
July 6, 2026 15:16
f214365 to
8570f64
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-6-github-reporting
branch
2 times, most recently
from
July 6, 2026 16:27
3d9c51f to
ced0bde
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/e2e-browserstack/phase-7-soft-launch
branch
2 times, most recently
from
July 6, 2026 16:36
9d963fc to
bf49ea7
Compare
This was referenced Jul 7, 2026
markmur
approved these changes
Jul 13, 2026
This was referenced Jul 14, 2026
Assisted-By: devx/6c1e3ad5-96c8-4972-b087-da7ff7b195c3
This was referenced Jul 14, 2026
Contributor
Author
Merge activity
|
This was referenced Jul 15, 2026
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?
I made a pivot in this branch - I was introducing a flag
E2E_STRICTthat would surface failures differently depending whether we wanted the pipeline to be "blocking" for PR merges. I realised this wasn't necessary as all we need is to add/remove the status check from the required checks for PR merge.It also led to problematic bugs in the pipeline where the e2e-report stage (that reports the comments back on the PR / posts the status checks) would be missing the artifacts it needs to report.
I removed all
E2E_STRICTusage, accepting the false branch, and we ratify at the e2e-report stage whether we received all the reports we need to post the status.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