Package: git_manager
A script that can handle multiple Git repositories locally. Written in
Python, supports version 3.5 and upwards.InstallationMake sure python is installed, then run# install from a clone of the repositorypythonsetup.pyinstallor# install from PyPipipinstallgit_managerto install the package. This will make it available by runninggit-manager(orgit manager).ConfigurationGit Manager can be configured through its configuration file. In order,
it looks for the configuration file in the following locations:$GIT_MANAGER_CONFIG(if set)~/.config/.gitmanager/config(or$XDG_CONFIG_HOME/.gitmanager/configif set)~/.gitmanagerThe configuration file is parsed line-by-line and declares which
repositories are under GitManager control. It consists of three
different types of directives:Root LineConfigure the root folder to clone repositories to
automatically. Starts with two hashes, then sets the folder relative
to the users home directory. For example:## /opt/repositoriesCommentsAnything starting with a “#” will be treated as a
comment. The same goes for empty (or whitespace-only) lines.Repository instructionTo declare a repository writeREPOSITORY_URL  [FOLDER]. This declares that the repository
fromREPOSITORY_URLshould be cloned into the folderFOLDER.
In case the folder is omitted, the ‘humanish’ part of the URI will be
taken automatically. All folder paths by default are relative to the
users home folder, but this can be changed with the instruction
below. Example:# makes the git/git repository available locally
# in the folder ~/Projects/git
https://github.com/git/git Projects/git

# makes the GitManager repository available
# in the folder ~/GitManager
https://github.com/tkw1536/GitManagerGroup InstructionIn the case where multiple repositories should
be cloned into the same folder, it is inconvenient to always give the
full path to that folder in the configuration file. For this reason
GitManager supports the concept of a group. A group can be started by
prefixing a line with the “>” character. A group takes one argument.
A path to a folder all repositories should be cloned into. This is
best illustrated in the form of an example:# We can create a group to store all our atom-related projects.
# All repositories are automatically available in the ~/AtomProjects
# folder.
> AtomProjects
  https://github.com/atom/atom
  https://github.com/atom/markdown-preview

# makes the GitManager repository available
# in the folder ~/GitManager
https://github.com/tkw1536/GitManagerGroups completely support nesting. A sub-groups path and
pattern for origin are relative to the parent group. To create a
sub-group, add another “>” character in front of the line.An example configuration file can be found in the fileconfig_example.Installing Repositories LocallySetupUsegit-manager setup [pattern]to clone repositories in the config file to the local disk.
Use the optional pattern argument to restrict the reposiories to install.CloneUsegit-manager clone [--save] urlto automatically clone a repository into a location determined by the URL.
Use the--saveflag to automatically update the config file.ReconfigureUsegit-manager reconfigureto automatically add repositories found in folder and it’s subdirectories to the configuration file.Viewing Local RepositoriesListUsegit-manager ls [pattern]to list local repositories.
Use the optional pattern argument to restrict the repositories to list.StatusUsegit-manager status [pattern]to show the status of local repositories.
Use the optional pattern argument to restrict the repositories to check.StateUsegit-manager state [pattern]to compare local repositories with their remote counterpart.
Use the optional pattern argument to restrict the repositories to check.Updating Local RepositoriesPullUsegit-manager pull [pattern]to rungit pullon all repositories installed locally.
Use the optional pattern argument to restrict the repositories to pull.FetchUsegit-manager fetch [pattern] [args...]to rungit fetchon all repositories installed locally.
Use the optional pattern argument to restrict the repositories to fetch.
Use the optional remaining arguments to pass further arguments to the fetch command.PushUsegit-manager push [pattern]to rungit pushon all repositories installed locally.
Use the optional pattern argument to restrict the repositories to pull.GCUsegit-manager gc [pattern] [args...]to rungit gcon all repositories installed locally.
Use the optional pattern argument to restrict the repositories to garbage collect.
Use the optional remaining arguments to pass further arguments to the gc command.Repository PatternsSome commands optionally accept thepatternargument. This can be
used to filter repository by their name.Repository patterns are simpleglob-likepattern matches on
standardized remote URLs. They can also be normal glob patterns on full
URLs.For example:PatternExamplesworldgit@github.com:hello/world.git,https://github.com/hello/worldhello/*git@github.com:hello/earth.git,git@github.com:hello/mars.githello/m*git@github.com:hello/mars.git,git@github.com:hello/mercury.gitgithub.com/*/*git@github.com:hello/world.git,git@github.com:bye/world.gitgithub.com/hellogit@github.com:hello/world.git,git@github.com:hello/mars.gitDevelopment and TestingThis project is unit tested with a high coverage rate. The tests can be
run with:nosetests--with-coverage--cover-packageGitManagerTests are automatically run on Travis CI after every commit.LicenseThe MIT License (MIT)

Copyright (c) 2016-18 Tom Wiesing

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.