Skip to content

feat: introduce invites and allow for inviting new users without creating an account for them #3226

feat: introduce invites and allow for inviting new users without creating an account for them

feat: introduce invites and allow for inviting new users without creating an account for them #3226

Triggered via pull request May 6, 2025 04:55
Status Success
Total duration 9m 39s
Artifacts 3
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

on_pr.yml

on: pull_request
Matrix: ci / ci
build-all  /  Emit container tag sha
5s
build-all / Emit container tag sha
build-all  /  ...  /  Build
3m 8s
build-all / build-base / Build
build-all  /  ...  /  Build
4m 1s
build-all / build-core / Build
build-all  /  ...  /  Build
2m 1s
build-all / build-jobs / Build
path-filter
4s
path-filter
close-preview  /  preview
close-preview / preview
Matrix: e2e / Integration tests
deploy-preview  /  preview
4m 34s
deploy-preview / preview
deploy-docs-preview  /  build-docs
1m 46s
deploy-docs-preview / build-docs
close-docs-preview
0s
close-docs-preview
status-check
3s
status-check
Fit to window
Zoom out
Zoom in

Annotations

1 error, 24 warnings, and 1 notice
[chromium] › playwright/member.spec.ts:123:7 › Community members › User needs to confirm their email address again if they change it during signup: core/playwright/member.spec.ts#L54
1) [chromium] › playwright/member.spec.ts:123:7 › Community members › User needs to confirm their email address again if they change it during signup Error: expect(locator).toBeVisible() Locator: getByText('No results.') Expected: visible Received: <element(s) not found> Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByText('No results.') 52 | await membersPage.addExistingUser("some@pubpub.org"); 53 | await membersPage.removeMember("some@pubpub.org"); > 54 | expect(page.getByText("No results.")).toBeVisible(); | ^ 55 | }); 56 | 57 | test("new user signup flow", async ({ browser }) => { at /home/runner/work/platform/platform/core/playwright/member.spec.ts:54:41
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L42
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L57
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L84
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L91
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L107
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L79
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L99
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L91
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L107
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L42
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L57
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L84
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L135
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L57
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L84
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L91
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L107
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L79
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L120
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L42
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L111
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
🎭 Playwright Run Summary
1 flaky [chromium] › playwright/member.spec.ts:123:7 › Community members › User needs to confirm their email address again if they change it during signup 9 skipped 103 passed (2.2m)

Artifacts

Produced during runtime
Name Size Digest
pubpub~platform~6K2C09.dockerbuild Expired
58.2 KB
sha256:5965f957d0c300c5b7a28e6f148d34b4b174112007a3c7c24baaa44bd1f0e609
pubpub~platform~PHZ27G.dockerbuild Expired
64.9 KB
sha256:1204c1f19e5e4071f3fabd4d0510b6731f56dee2c294baaeff84d68d739ba82a
pubpub~platform~PUKS4Q.dockerbuild Expired
59.7 KB
sha256:95339ecbd00e92b95e3a64a6998214640642cc3a2223956832ef1f1b98aed413