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

Run GitHub actions tests on Jupyter notebooks #62

Open
sgbaird opened this issue Dec 11, 2022 · 0 comments
Open

Run GitHub actions tests on Jupyter notebooks #62

sgbaird opened this issue Dec 11, 2022 · 0 comments

Comments

@sgbaird
Copy link
Contributor

sgbaird commented Dec 11, 2022

Describe your use-case

Too often, the tutorial notebooks I make go out-of-sync with the rest of the codebase, especially if the tutorials were developed early on. Sometimes I catch the issues beforehand, sometimes I catch them after it's been released, and other times, people tell me that one of the notebooks isn't working anymore.

Describe the solution you would like to see for your use-case

Some option from sparks-baird/self-driving-lab-demo#146, maybe nbmake? I think the user should be able to specify which notebook(s) to run, and that it should be minimal at first (maybe just an example notebook). Lmk if you think this seems in-scope.

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