git-workspace :rocket:

If your company has a large number of repositories and your work involves jumping between a lot of them, then git-workspace can save you some time by:

• Easily synchronizing your projects directory with Github, Gitlab.com or Gitlab self-hosted :wrench:
• Keep projects consistently named and under the correct path :file_folder:
• Automatically set upstreams for forks :zap:
• Move deleted repositories to an archive directory :floppy_disk:
• Allowing you to access any repository instantly :shipit:
• Execute git fetch on all projects in parallel :godmode:

This may sound useless, but the "log into your git provider, browse to the project, copy the clone URL, devise a suitable path to clone it" dance can be a big slowdown. The only obvious solution here is to spend more time than you'll ever spend doing this in your whole life on writing a tool in Rust to do it for you.

Table of Contents

• Install :cd:
  • Homebrew (MacOS Linux)
  • Binaries (Windows)
  • Cargo
• Usage :saxophone:
  • Define your workspace
  • Provider credentials
  • Adding providers
  • Updating your workspace
  • Fetching all changes
• Switch projects :repeat:
  • Fish, with fzf
• Contributing :bug:

Install :cd:

Homebrew (MacOS + Linux)

brew tap orf/brew, then brew install git-workspace

Binaries (Windows)

Download the latest release from the github releases page. Extract it and move it to a directory on your PATH.

Cargo

Don't do this, it's pretty slow: cargo install git-workspace

Usage :saxophone:

Git is really annoying and hijacks the --help flag for subcommands. So to get help use git-workspace --help, not git workspace --help.

Define your workspace

A workspace is the directory that git-workspace will manage for you, filling it with projects cloned from your providers. To configure this just set a GIT_WORKSPACE environment variable that points to an empty directory. For example:

export GIT_WORKSPACE=~/projects

Provider credentials

Both Github and Gitlab require personal access tokens to access their GraphQL endpoints. Create an access token here:

• Github: https://github.com/settings/tokens (Just the repo scope)

• Gitlab: https://gitlab.com/profile/personalaccesstokens (Just the api scope)

Export these tokens as GITHUB_TOKEN and GITLAB_TOKEN in your shell.

Adding providers

You can use git workspace add to quickly add entries to your workspace.toml:

• Clone all github repositories for a user or org

  • git workspace add github [USER OR ORG NAME]

• Clone a namespace from Gitlab:

  • git workspace add gitlab group gitlab-ce/gitlab-services

• Clone from a self-hosted gitlab instance:

  • git workspace add gitlab group my-company-group --url=https://internal-gitlab.company.com

Updating your workspace

Running git workspace update will:

1. Fetch all repositories from your providers
2. Clone any new repositories that are not present locally
3. Move any deleted repositories to $GIT_WORKSPACE/.archived/ for posterity

Fetching all changes

git workspace fetch will run git fetch on all projects.

Switch projects :repeat:

git workspace list will output the names of all your projects. You can integrate this with whatever tool you wish to provide a way to quickly search for and select repositories.

Fish, with fzf

The following fish shell snippet gives you a open-project [search-string] command you can use to search for and open projects. It combines the git workspace list command with fzf, and opens the project path with your $EDITOR:

```fish

~/.config/fish/functions/open-project.fish

function open-project -d "Open a project" set filter "$argv" set chosenproject (git workspace list | fzf -q "$filter") if string length -q -- $chosenproject $EDITOR $GITWORKSPACE/$chosenproject pushd $GITWORKSPACE/$chosenproject end end ```

Contributing :bug:

This is my first 'proper' Rust project. If you're experienced with Rust you might puke at the code, but any feedback to help me improve would be greatly appreciated!

If you want to contribute then just go for it. cargo install should get you ready to go. Be warned: there are currently no tests :bomb:. I run integration tests with Github Actions, but that's about it. It's on my to-do list, I promise :tm:.