-
Notifications
You must be signed in to change notification settings - Fork 55
Switch to GitHub actions on CI #91
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
Conversation
cc @fcollonval @ianhi since this was discussed in #86. Example run in the fork: https://github.com/jtpio/widget-ts-cookiecutter/runs/2011603959 For now this PR skips tests and docs, just so we can have a basic workflow working for other PRs. But we should eventually add them back, and also check the generated workflow from the cookiecutter is also correct. |
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 thanks!
# Make sure our lab extension was installed. | ||
jupyter labextension list 2>&1 | grep -ie "jupyter-widget-testwidgets.*OK" | ||
# Make sure our lab extension can be linked. | ||
jupyter labextension link |
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.
On the PR for jlab3 we can update this to check if jupyter labextension develop . --overwrite
works.
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.
yes absolutely we can do that in #90
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.
Done in 400a790
Extracting the GitHub Actions part of #86, so it can be used for other PRs such as #90.