Skip to content

Usdk-e2e status check on PRs - #108

Merged
bpapillon merged 3 commits into
mainfrom
sdk-e2e-status-check
Sep 6, 2026
Merged

Usdk-e2e status check on PRs#108
bpapillon merged 3 commits into
mainfrom
sdk-e2e-status-check

Conversation

@bpapillon

@bpapillon bpapillon commented Sep 6, 2026

Copy link
Copy Markdown
Collaborator

For the SDK E2E suite (SchematicHQ/actions#565): sdk-e2e-status.yml posts an sdk-e2e commit status on every PR, pending on update-wasm-v* bump branches until the schematic-api E2E run reports back and success immediately on anything else. This lets sdk-e2e become a required check without blocking ordinary PRs.

This SDK has no configurable Redis key prefix, so the testapp needs no change for the new replicator-docs mode.

Posts an sdk-e2e commit status: pending on update-wasm-v* bump branches
until the schematic-api SDK E2E run reports back, success on every other
PR, so sdk-e2e can be a required check without blocking normal PRs.
Copy of schematic-replicator/testdata/redis_key_layout.json; the Redis
provider prefix plus the datastream key must reproduce the keys the
replicator writes (SCH-7070).
@bpapillon
bpapillon marked this pull request as ready for review September 6, 2026 05:10
@bpapillon
bpapillon requested a review from a team as a code owner September 6, 2026 05:10
@bpapillon
bpapillon merged commit a9e7521 into main Sep 6, 2026
4 checks passed
@bpapillon
bpapillon deleted the sdk-e2e-status-check branch September 6, 2026 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants