However, if you clone a GitHub repo to your Drive folder, you can access it anytime. Accessing Google Drive from Google Colabīecause by default the directories that you can access from Colab are not the ones on your Drive, it would make it very hard (if at all possible) to access those files later. But let me explain how I solved both issues and am now able to clone any repo to my Google Drive, edit my ipynb files from Colab and push everything back to GitHub even from my iPad Pro. And look, I’m sure that you could solve the credentials problem in some other way, but I was in a hurry, and so the solution may not have been the best or more secure. And also, if I tried to push back to the remote, that failed because Colab never prompted me to enter my GitHub credentials. I had managed to clone my repo, as you would, to the content folder that is enabled for your Google Colab notebook, I could see my ipynb files listed right there, and yet I was unable to open them. Also, when it comes time to push everything back to the remote, it simply will fail (no way to enter the credentials). This means that if you were to directly clone a GitHub repo, it will end up in some directory that you won’t easily find from outside Colab (if at all). ![]() ![]() ![]() The reason why cloning a GitHub repository with Google Colab is not as straight forward as one may think is twofold:īy default, you don’t have an easily accessible File System
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |