Skip to content

Preserve email value when switching login type #24

Preserve email value when switching login type

Preserve email value when switching login type #24

Triggered via pull request January 25, 2025 02:52
Status Success
Total duration 46s
Artifacts

pr-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
lint: src/app/(uc)/signin/page.js#L39
Missing semicolon
lint: src/app/(uc)/signin/page.js#L56
Missing trailing comma
lint: src/app/(uc)/signin/page.js#L64
Missing semicolon
lint: src/app/(uc)/signin/page.js#L66
Missing semicolon
lint: src/app/home/Contributor.js#L142
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
lint: src/app/oauth/page.js#L89
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
lint: src/app/quiz/[id]/page.js#L95
Missing semicolon
lint: src/app/shilling/[id]/page.js#L176
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
lint: src/app/u/[handle]/Banner.js#L75
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
lint: src/entry/components/Header/CustomConnectButton.js#L137
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element