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

Move CI to github actions #174

Closed
arlyon opened this issue Apr 26, 2021 · 1 comment
Closed

Move CI to github actions #174

arlyon opened this issue Apr 26, 2021 · 1 comment

Comments

@arlyon
Copy link
Collaborator

arlyon commented Apr 26, 2021

This is mainly for discussion. I have done some work on arlyon/async-stripe to move to github actions for formatting and tests which I personally prefer over travis as it keeps things on-platform and displays errors inline on the PR. I can prepare a PR for it if that is something we are interested in.

@kestred @seanpianka

Additionally, on my fork, I set it to auto generate schema changes once a week, however that required a bit of work as I wanted to draw a clean seperation between hand-authored and machine-generated code, namely moving all the generated code into a generated subfolder. Happy to merge these changes as well, but just wanted to get the a-ok.

See here for an example: arlyon/async-stripe#45

Cheers!

Alex

@arlyon
Copy link
Collaborator Author

arlyon commented Oct 29, 2022

Closing now that async-stripe in the de-facto successor

@arlyon arlyon closed this as completed Oct 29, 2022
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

No branches or pull requests

1 participant