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

Test gqlgen generate in CI #2017

Merged
merged 1 commit into from
Mar 1, 2022
Merged

Test gqlgen generate in CI #2017

merged 1 commit into from
Mar 1, 2022

Conversation

mtibben
Copy link
Member

@mtibben mtibben commented Mar 1, 2022

The gqlgen init already tested in CI should be followed up with another gqlgen generate to prevent regressions like the one seen in #1849.

gqlgen init should also return an error if the generation step fails.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 74.455% when pulling b862f58 on test-generate-in-ci into 3a9413f on master.

@StevenACoffman StevenACoffman merged commit 839b50d into master Mar 1, 2022
@StevenACoffman StevenACoffman deleted the test-generate-in-ci branch March 1, 2022 12:11
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