-
Notifications
You must be signed in to change notification settings - Fork 2
Set up CI for report generation. #7
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
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Brad Dettmer <[email protected]>
|
Oops, I meant to submit a pull request against my |
|
Yay! Fixes #4 :) The PDF export is automatically updated and lives here: https://mkcor.github.io/case_studies_Py/rosi_py/rosi_py.pdf We could make builds faster by using container-based infrasture (see also checklist in the main PR description) and improve the project organization (see #5 and the following). But, for now, it works! I decided to use the @bayesways Please review! Thanks. |
This is only a test, to trigger a Travis CI build and see if build artifacts land at: https://mkcor.github.io/case_studies_Py/
I haven't completed everything:
rosi_py.texfile./cc @bayesways @redSlug