-
Notifications
You must be signed in to change notification settings - Fork 660
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
[docs] Move jupyter notebooks to DJL Demo #2854
Conversation
we also have a job that just run those notebook and append output result, does that still work with this change? |
Are you referring to the docs action? I updated that one (and it won't pass until both changes are merged) so this PR is not expected to pass CI |
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #2854 +/- ##
============================================
+ Coverage 72.08% 72.30% +0.21%
- Complexity 5126 7162 +2036
============================================
Files 473 708 +235
Lines 21970 31908 +9938
Branches 2351 3313 +962
============================================
+ Hits 15838 23070 +7232
- Misses 4925 7259 +2334
- Partials 1207 1579 +372 ☔ View full report in Codecov by Sentry. |
This moves the notebooks to the demo repositories. It makes it more clearly follow the trend where the things in the main repo are master build while those in demos track nightly snapshots or releases.
c2388b0
to
2ce1cca
Compare
* [docs] Move jupyter notebooks to DJL Demo This moves the notebooks to the demo repositories. It makes it more clearly follow the trend where the things in the main repo are master build while those in demos track nightly snapshots or releases.
This moves the notebooks to the demo repositories. It makes it more clearly follow the trend where the things in the main repo are master build while those in demos track nightly snapshots or releases.
Combined with deepjavalibrary/djl-demo#390