gh access token not required (?)
Opened this issue · 4 comments
Maybe I'm missing something, but why would one need to create a gh access token to simply clone a public (!) repository? Your instructions also don't tell them to fork it, so they would not have write permissions there either...
I think we can remove this part of the setup :)
also a bit confusing how to open the notebook from colab after downloading.. seems colab can only read fiels under Colab Notebooks folder. In this tutorial files are downloaded in the Githubs folder and they are invisible.
Hmm, that worked for me though. I was just navigating to the Github folder on my google drive and then double-clicking and they opened in Colab. Does that work for you?
No, nothing appears there.. I can only download them, but cannot run them
Problem solved:
The python notebook files should not be opened in the colab.research.google.com through the "file" menu. Instead, they should be opened in the google drive website. The files will be automatically opended with colab.