After an unexpected need to reset my work machine ๐, and needing to set up my development environment again by hand ๐ ๏ธ, I decided to create a solution to quickly restore my local git repositories (and associated folder structure) ๐.
I took this opportunity to write two bash scripts that clone and update all repositories on GitHub belonging to either a user or an organization ๐ฆ.
This means that, for example, with a single command โจ๏ธ, you can clone hundreds or thousands of repositories, with high levels of concurrency (50 clones in parallel is doable ๐จ).
The scripts allow for a configurable clone depth, a limit for the number of repositories cloned, and a level of concurrency that decides how many clones are run in parallel ๐.
By running the following command:
git-clone-all --owner f3rno64 --limit 200 --jobs 40 --dir ./f3rno64
I was able to clone all 174 personal repositories ๐, with full commit histories and all tags & branches, in 58 seconds โฑ๏ธ.
I wrote a blog post describing this in more detail here ๐, check it out for a breakdown of the arguments and examples of usage.
The GitHub repository is f3rno64/mass-git-scripts and the README also includes examples and general usage instructions ๐๏ธ.
Please check it out and let me know what you think! ๐ฌ
I hope you find it useful, and any feedback or suggestions for improvement would be greatly appreciated! ๐
No, I've never heard of it. It looks interesting and offers more functionality in a structured way, but it's also unmaintained and hasn't had any activity for a long time.
I'll use it as an inspiration to implement more features and develop the setup of scripts I've already written into a full-fledged command line tool.
Thank you for the idea! ๐ I'm curious what this will lead to.
A feature I use constantly is the threading.
Iโve been using
mrsince the raspberry pi and Ubuntu days. It allowed me to keep my remote clones up to date. I created a few bash scripts for populating the registry.