Add repo subcommand to operate on collection of repos
#22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kattrali
reviewed
Jul 22, 2018
| Repo | ||
| ==== | ||
|
|
||
| Commands to operate on a collection of repositories at a time. |
There was a problem hiding this comment.
The summary should mention that this functionality is git-specific
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes you might want to perform some bulk operation on a collection of repositories, for example adding and committing a file. Checking they are all synced, or even running reports by checking a collection of repositories.
The
maintain repogroup brings a collection of sub-commands to operate on multiple repos. Right now it looks for all.gitrepos in subdirectories, in the future I want to be able to provide configuration or dynamic providers. You should be be able to define the repos to use and their paths in a config file so that you can use them to perform actions even if you don't have repos locally, for example masscloningall of them on a new system. Another type of repo list "provider" I'd like to see is a dynamic one, for example to populate all of the repos in a GitHub org or user so that you can mass clone an entire org/user.reponame make sense for subcommand? Couldgitorreposmake more sense?