-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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(notebook): copy configs files from Google Drive #1064
Conversation
Changes: - Added "import" for configs files - Changed "clone" to export for configs files
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1064 +/- ##
=======================================
Coverage 19.25% 19.25%
=======================================
Files 39 39
Lines 3496 3496
Branches 497 497
=======================================
Hits 673 673
Misses 2804 2804
Partials 19 19 ☔ View full report in Codecov by Sentry. |
|
Thanks for your suggestion. It would be nice to have an error handling and an explanation that this operation is optional to avoid confusion. |
Ok, I'll do it when I am home |
How do you mean error handling? |
Added backing up when importing and exporting because maybe you accidentally override the config.json when importing/exporting. Just in case
@allcontributors add Onako2 docs |
I've put up a pull request to add @Onako2! 🎉 |
Changes:
Description of change
Made that you can also import the configs files from Google Drive because it takes long if you have to do it every time to copy paste the files.
The Pull Request Fixes #1063
Pull-Request Checklist
main
branchFixes #1063
pre-commit run -a
passes with this change or ci passespoetry run pytest
passes with this change or ci passes