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

Adding GitHub checks #7

Merged
merged 12 commits into from Jul 18, 2023

Conversation

gitstart
Copy link
Contributor

CLoses out issue: FLOW-GS-2

@vercel
Copy link

vercel bot commented Jun 29, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
google-calendar-api ⬜️ Ignored (Inspect) Jul 18, 2023 4:24am

@ghost
Copy link

ghost commented Jun 29, 2023

👇 Click on the image for a new way to code review

Review these changes using an interactive CodeSee Map

Legend

CodeSee Map legend

@gitstart gitstart marked this pull request as ready for review June 29, 2023 10:46
@gitstart
Copy link
Contributor Author

Hi @richardguerre this pr is ready for review.

NB: The backend tests is failing and stuck in a loop . You can create a separate ticket for that if you would like us to fix that.

Co-authored-by: MayanjaAndrew <68685849+MayanjaAndrew@users.noreply.github.com>
Copy link
Owner

@richardguerre richardguerre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good start and I will merge it in if you just fix the server test running in an infinite loop issue.

Comment on lines 3 to 6
inputs:
ssh-private-key:
description: "SSH key used for private git clone"
required: true
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this for? The GitHub actions seem to work fine without any "input".

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. It's not needed. We'll remove it.

- name: Use Node.js
uses: actions/setup-node@v3
with:
node-version: "18.13.0"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check the version in .nvmrc or even try and use the version in .nvmrc using cat .nvmrc. This issue seems to point out how to do it.

.github/workflows/checks.yml Show resolved Hide resolved
- name: Prisma Gen
run: npm run gen -w apps/server
- name: Test check
run: npm run test -w apps/server
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason this check is in a loop is because vitest runs in watch mode in a development environment and in run mode when process.env.CI is truthy. Normally GitHub actions already insert CI=true as part of environment variables. You can try adding manually right below the DATABASE_URL env.

@richardguerre
Copy link
Owner

Also why was this not done as part of #2? Can you try not to create duplicate PRs?

- Prisma gen doesn't migrate the DB with the latest tables which might be why the tests were stuck in an infinite loop.
- Check if using `npm run db:dev` instead of `gen -w apps/server` works by running `Item.test.ts`
@richardguerre richardguerre merged commit 8714b54 into richardguerre:main Jul 18, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants