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: fix CI #16
Chore: fix CI #16
Conversation
…there is no package.json
Not sure why the CI is failing, |
1e78fa3
to
2f00ae9
Compare
…void dependency on library builds)
2f00ae9
to
483ae01
Compare
… CI runs the integration tests
I’ll move the keys into Travis. On my phone but will review it more thoroughly when I get home. Thanks for your work here. Great seeing a green check mark |
22e9fb1
to
08115d9
Compare
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.
Looks good to me, merge when ready
rudy-src-main
entry point is used by the boilerplate for all libraries in the repo, even for production buildsrudy-src-main
on some librariesbuild
script on libraries so that they do actually get built before the integration tests run