Skip to content

Add an ON DELETE CASCADE for oauth_openid_requests #22708

Add an ON DELETE CASCADE for oauth_openid_requests

Add an ON DELETE CASCADE for oauth_openid_requests #22708

Triggered via pull request December 10, 2025 23:13
Status Success
Total duration 4m 6s
Artifacts 5

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
coverage-report
main is missing merged-coverage.xml. See documentation on how to add this
coverage-report
No artifacts found for the following workspaces: ci,cron
Legacy key/value format with whitespace separator should not be used: Dockerfile#L36
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/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L50
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L47
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG ruby:${RUBY_VERSION}-slim results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L96
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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L37
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#L55
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#L50
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L39
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SECRET_ACCESS_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L38
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/

Artifacts

Produced during runtime
Name Size Digest
minitest-coverage
48.7 KB
sha256:db751b145737f412823cf0bb24d8aacd927575f1fe5df08a74c989de0cdad297
minitest-reports
25.9 KB
sha256:813525b1f29956463c69345ca3dd587ff43d8b3c4df77ef35e4ae1a2e4113b40
neinteractiveliterature~intercode~MJ53SH.dockerbuild
130 KB
sha256:4c6616db03a43b5e9efa241c5a39618ecddb47ef6dcb46c44ca5dcce4f455b38
vitest-coverage
89.4 KB
sha256:101aa8c26d6557f50d516e04f1d04e3db2c426232542e162f48897b267ff9b90
vitest-reports
537 KB
sha256:78e4030551038d7beeb1986962d003111f1d0b8b0c260b46402296743571d28a