If no configuration is found ghorg will use its defaults and try to clone a GitHub Org, however an api token is always required. This file comes from the sample-conf.yaml. Precedence for configuration is first given to the flags set on the command-line, then to what's set in your $HOME/.config/ghorg/conf.yaml. Note, some features may be different for certain providers. There is a handy chart thanks to GitLab that translates terminology here. GitLab and BitBucket use different terminology.

The terminology used in ghorg is that of GitHub, mainly orgs/repos. If you want to work out of this directory, make sure you either rename the directory or set the -no-clean flag on all future clones to prevent losing your changes locally. So when running ghorg a second time on the same org/user, all local changes in the cloned directory by default will be overwritten by what's on GitHub. If repo does exists locally in the clone directory it will perform a git pull and git clean on the repo.Will clone a repo if its not inside the clone directory.With default configuration ghorg performs two actions. Onboarding new team members (cloning all team repos).Searching an orgs/users codebase with ack, silver searcher, grep etc.This can be useful in many situations including Use ghorg to quickly clone all of an orgs, or users repos into a single directory.

How to install gitlab from source