Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: explicitly setup node and run yarn install before running specs #459

Merged
merged 1 commit into from
Aug 10, 2023

Conversation

G-Rath
Copy link
Contributor

@G-Rath G-Rath commented Aug 3, 2023

Technically API-only apps won't need this but we pretty much never do those and this shouldn't error so at worse it'll just add a couple of seconds to CI.

Resolves #456

@G-Rath G-Rath added the bug Something isn't working label Aug 3, 2023
@G-Rath G-Rath merged commit eeadd3c into main Aug 10, 2023
21 checks passed
@G-Rath G-Rath deleted the install-node-for-rspec branch August 10, 2023 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Node should be setup and assets explicitly built for ruby/rspec job
3 participants