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
Currently, the slowest GitHub actions are the docker builds. The only ways the docker builds would fail are:
a new top level file or directory that is COPY-ed is added or removed
npm ci or npm run build fail
cargo build fails
the Dockerfile includes changes that need iteration
npm ci/run build and cargo build are covered directly by other GitHub actions
In order to mitigate against merging breaking changes to main, we could run the docker builds IFF the list of top level files has changed, or if the Dockerfile has changed
The text was updated successfully, but these errors were encountered:
Currently, the slowest GitHub actions are the docker builds. The only ways the docker builds would fail are:
npm ci
ornpm run build
failcargo build
failsnpm ci/run build
andcargo build
are covered directly by other GitHub actionsIn order to mitigate against merging breaking changes to main, we could run the docker builds IFF the list of top level files has changed, or if the Dockerfile has changed
The text was updated successfully, but these errors were encountered: