You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the the docs, we're using the danger/danger-js GHA action (docker-based) for running the checks in CI without installing Yarn.
It prints the warnings
Build container for action use: '/home/runner/_work/_actions/danger/danger-js/92d2525fe338bff16ae7d42794d0a835e2d27473/Dockerfile'.
/usr/bin/docker build -t 079b50:eead83866dcc40a99e8beb9b679b5b8a -f "/home/runner/_work/_actions/danger/danger-js/92d2525fe338bff16ae7d42794d0a835e2d27473/Dockerfile" "/home/runner/_work/_actions/danger/danger-js/92d2525fe338bff16ae7d42794d0a835e2d27473"
...
2 warnings found (use docker --debug to expand):
- FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 11)
- FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1)
The Docker container should build successfully and the workflow complete without warnings
Your Environment
software
version
danger.js
v12.3.3
node
npm
Operating System
EDITED
I was mistaken about the error - it's just a warning from GHA - it doesn't actually prevent the workflow from completing.
Still, it would be nice to fix it (sounds simple enough?)
The text was updated successfully, but these errors were encountered:
amakhrov
changed the title
[BUG] Error when using with the GitHub Action: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1)
[BUG] Warning when using with the GitHub Action: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1)
Jan 21, 2025
Describe the bug
As per the the docs, we're using the
danger/danger-js
GHA action (docker-based) for running the checks in CI without installing Yarn.It prints the warnings
Workflow:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Docker container should build successfully and the workflow complete without warnings
Your Environment
EDITED
I was mistaken about the error - it's just a warning from GHA - it doesn't actually prevent the workflow from completing.
Still, it would be nice to fix it (sounds simple enough?)
The text was updated successfully, but these errors were encountered: