Skip to content

🎨 #263 Footerに外部送信ポリシーを追加 #571

🎨 #263 Footerに外部送信ポリシーを追加

🎨 #263 Footerに外部送信ポリシーを追加 #571

Triggered via push August 1, 2024 14:19
Status Success
Total duration 1m 35s
Artifacts

ci.yml

on: push
Matrix: Build And Test
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build And Test (20.x)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build And Test (20.x): src/app/en/layout.tsx#L55
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font
Build And Test (20.x): src/app/layout.tsx#L55
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font
Build And Test (20.x): src/components/Upload/UploadModal/CreatedLgtmImage.tsx#L32
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
Build And Test (20.x): src/components/Upload/UploadModal/UploadModal.tsx#L109
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