GitHub Repository Manager
VS Code extension that lists your personal and organizations GitHub repositories, allowing you to clone and access them and create new ones
This gif is a little old! We are now using the VS Code GitHub login system and the extension is prettier! The gif will be eventually updated!
Cloned Repositories Search
To make your GitHub cloned repositories show up in the Cloned tree view, you will need to set the
"git.defaultCloneDirectory" on your VSCode
settings.json file to an absolute path where your cloned repositories are located (may be deep). On Linux you may use "~" to point to your home directory. On Windows, you must use the
I store my repos under "~/Dev", so that's what I use as my "git.defaultCloneDirectory" value.
Creating a repository
While hovering the REPOSITORIES tree view title, a plus (+) button appears. Click on it, and enter the new repository name, description (optional) and visibility. On success, you may choose to clone the new repository.
Always Clone To Default Directory
Always clone to the directory specified in "git.defaultCloneDirectory".
Colors the repositories icons.
Default Clone Directory Maximum Depth
How deep on
"git.defaultCloneDirectory" the cloned repositories will be searched. A depth of 0 means it will only search in the directory itself, a depth of 3 means it will search up to 3 directories below.
Directories To Ignore
Directories names that our cloned repositories searcher will ignore.
Default: ["node_modules", ".vscode", ".git"]
Search and clone public repositories
Only show Repository creation icon when logged
Git not installed message
Other repositories found by the Cloned Repository Searcher. Useful for quickly opening a repository you don't own.
Visualize without cloning (useful for getting some value or checking something from some repository)
"Order by" (alphabetically, stars, your open frequency, created on, updated on) in top menu
Search repository by name
Fetch repositories on demand - Some devs have hundreds or thousands of repos. Instead of fetching all of them on init and displaying all of them together, there could be a [1..100], [101, 200] tree system, for both on demand fetch and display.
Remove cloned from local if it isn't dirty (= not locally diff from github)
Feel free to open an issue for features requests, problems or questions!
For developing: clone it, run
npm start and run the debugger.