Skip to content
PR

Ticket #199 and ticket #213 #467

Sign in to view logs

Ticket #199 and ticket #213

Ticket #199 and ticket #213 #467

Triggered via pull request November 3, 2023 04:35
@BrettEastmanBrettEastman
synchronize #228
edit-button2
Status Success
Total duration 2m 50s
Artifacts –

pr.yml

on: pull_request
type-check
1m 36s
type-check
lint
2m 40s
lint
test
2m 7s
test
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
type-check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint: src/components/uploadPicture/uploadImage.tsx#L120
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element
lint: src/components/uploadedFile/uploadedFile.tsx#L26
Using `<img>` could result in slower LCP and higher bandwidth. Use `<Image />` from `next/image` instead to utilize Image Optimization. See: https://nextjs.org/docs/messages/no-img-element