Add Continuous Integration using Github Actions #223
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@XeR can you have a look again? |
The query results should be type checked properly in the future.
|
The changes have been updated for the recent v3 release. |
JJ-8
approved these changes
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This builds the frontend and backend using Node.js
16, 18, 19, and 20 and checks if the database migrations apply on a fresh database. It verifies the generated graphql bindings are up-to-date too.To allow to verify database migrations, I've added a
DB_MIGRATE_ONLYenvironment variable, which causes the api to exit after processing the migrations.In a separate step it runs linting steps as
eslintandprettierto catch style problems.We could run
docker compose buildas well just to verify the docker setup works? I didn't go for this in the first place, since you don't haveyarnin the frontend container anymore to verify the codegen.