This post is not incompatible with that flow, assuming you use GitHub it's quite likely you will eventually start using the gh cli command. Going back to the terminal, using only GitHub, one can backup all personal, org, or someone else's repos using the following script:
export GH_USER="0-vortex";
gh repo list $GH_USER--limit 99999 |
while read-r repo _;do
if[[$repo=~ "^($GH_USER/*)"]];then
gh repo clone $repofi;sleep 0.3;done
The above code clones the code with all its history, but manipulating the gh line one can fine tune that based on preferences, cloud provider, etc.
Thanks for your feedback and your perspective.
This blog post is based on my perspective and advice as someone who works at GitHub and teaches a group of people web development skills twice a year. Before we dive into Git and the terminal, I found that it's helpful to introduce them to GitHub via a GUI because they get to understand the difference concepts such as (push, pull, commit).
Then, when they learn Git they have more context around the workflow and commands.
I wouldn't use GitHub if you don't use Git properly. I'd rather use Dropbox, Drive, an HDD or even OneDrive.
This post is not incompatible with that flow, assuming you use GitHub it's quite likely you will eventually start using the
ghcli command. Going back to the terminal, using only GitHub, one can backup all personal, org, or someone else's repos using the following script:The above code clones the code with all its history, but manipulating the
ghline one can fine tune that based on preferences, cloud provider, etc.Don't forget to change the username!
Just a small suggestion: you can rewrite this to have the command directly in the loop.
Also using
whoamiin the assumption that your linux username is the same as your github username :DI like the one-line improvement but the username is definitely not a given for a lot of people :D
Yep, that's just a suggestion for cases where it's the same; my username is the same everywhere so for me this would work :D
Wow! That script is great. I will start using it in GCP or my machine, probably. Thanks dude!
no worries, glad it helps you!
Thanks for seeing my point of view @0vortex !!! Also wow, I just tried out your script..pretty cool 😎
awlays welcome! it feels like the gh cli is the natural bridge between the desktop experience and full time terminal usage :D
Thanks for your feedback and your perspective.
This blog post is based on my perspective and advice as someone who works at GitHub and teaches a group of people web development skills twice a year. Before we dive into Git and the terminal, I found that it's helpful to introduce them to GitHub via a GUI because they get to understand the difference concepts such as (push, pull, commit).
Then, when they learn Git they have more context around the workflow and commands.
Oh! That's an interesting point of view. Yes, I agree.
How are you doing it ??