-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: github actions workflow for tests / visual regressions #21
Conversation
@jennifer-richards now that we've got unit tests I've added a workflow to run those, TS, and linting on CI. Because the Nuxt build and TS require the generated API client we'll need to have the client on CI. It would be best to generate that on CI so that we have current types, but as we can't do that yet I've temporarily commited the API client (which is a single file) to test this workflow. |
.github/workflows/tests.yml
Outdated
- name: Setup Node | ||
uses: actions/setup-node@v3 | ||
with: | ||
node-version: 23.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would avoid using non-LTS versions in anything unless absolutely necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah it was the quickest fix for this... I'll look for a workaround
https://github.com/ietf-tools/rfced-www/actions/runs/12311686063/job/34362303820
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
generated
directoryvis-reg-test.yml
to the more readablevisual-regression-test.yml