actions-yarn | GitHub Action for interacting with yarn | Continous Integration library

Using defaults with run will only be applied to the run step (e.g scripts/commands that you execute yourself and not actions). See the docs:

Provide default shell and working-directory to all run steps in the job. Context and expression are not allowed in this section.

When you are using a GitHub action (you have uses:) it not possible to change the working directory. Keep in mind that some actions support this - you can pass an additional argument to with:, but in your case borales/actions-yarn do not support that.

What can you do?

As suggested in the borales/actions-yarn REAME.md:

Please keep in mind that this Action was originally written for GitHub Actions beta (when Docker was the only way of doing things). Consider using actions/setup-node to work with Yarn. This repository will be mostly supporting the existing flows.

You can remove these actions and call yarn directly in run:. Your workflow should look like:

gatsby-plugin-sharp, according to the documentation:

• @babel/runtime
• async
• bluebird
• filenamify
• fs-extra
• gatsby-core-utils
• gatsby-telemetry
• got
• imagemin
• imagemin-mozjpeg
• imagemin-pngquant
• lodash
• mini-svg-data-uri
• potrace
• prob-image-size
• progress
• semver
• sharp
• svgo
• uuid
• Dev dependencies: @babel/cli, @babel/core, @types/sharp, babel-preset-gatsby-package, cross-env, gatsby-plugin-image, gatsby-plugin-utils

On the other side, mozjpeg has:

• bin-build
• bin-wrapper
• logalot
• Dev dependencies: ava, bin-check, compare-size, execa, tempy, xo

From the error message you can see that the browser is being sent to http://project.example.com/... which doesn't exist, and even if it did wouldn't be where your test app is running. Assuming you're running the same test config locally, it's possible you have project.example.com pointed at localhost/127.0.0.1 (check your /etc/hosts or local DNS configuration) which would make your tests work there. You need to update your test configuration so tests run against whichever ip your app under test is being run on.

As we found out in the comment discussion, this was due to the fact that database.yml was not committed to the repository, and therefore leaving rails without the understanding of which database to use, and with what credentials.

The reason I am posting this answer here, is to share how we do commit database.yml to production, while still maintaining the necessary security guideline of "not having secrets committed to source control".

Since all of Rails configuration files support ERB, you can use it to define secrets using environment variables. For example: