This component helps querying remote services, like BitBucket and GitHub to get a list of repositories and helps cloning them locally for use or backup. It provides an API and a command line interface utility, read below for more information.

The requirements are specified in the composer.json file:

• PHP version >=5.5
• symfony/console version >= 2.4
• symfony/filesystem version >= 2.4
• ggioffreda/git version >= 0.1.3
• guzzlehttp/guzzle version >= 6.0
• league/event version >= 2.0

This component is available for installation through composer. From command line run:

$ composer require "ggioffreda/git-guardian" "~0.1"

Or add the following to your composer.json in the require section:

"require": {
    "ggioffreda/git-guardian": "~0.1"
}

For more information check the project page on Packagist.

You can use the Gioffreda\Component\GitGuardian\GitGuardian class to bulk clone your repositories into a destination. The following is an example on how to do so:

<?php

use Gioffreda\Component\GitGuardian\GitGuardian;

$guardian = new GitGuardian();
$emitter = $guardian->getEmitter();

// initialise your remote adapters

foreach ($remotes as $remote) {
    $guardian->addRemote($remote);
}

$guardian->cloneAll('/var/lib/repositories');

The GitGuardian class emits a range of events that allows you to monitor the status:

• git_guardian.pre_clone_remote and git_guardian.post_clone_remote are emitted before and after the list of repositories for a given remote is fetched and before they are cloned, one by one. These are emitted only once per remote adapter.
• git_guardian.pre_clone_repository and git_guardian.post_clone_repository are emitted before and after a repository is cloned from a remote. If the repository has been cloned already the system will try and fetch all changes instead of cloning it, so these events might not be called in favour of the following events;
• git_guardian.create_git is emitted when the repository had been cloned already in the same destination and therefore had not beel cloned;
• git_guardian.pre_fetch_repository and git_guardian.post_fetch_repository are emitted when the local repository was already available at cloning time and the changes are fetched ($ git fetch --all). These events will not be emitted if there's nothing to fetch;
• git_guardian.config_skip_repository to increase performance and avoid pointless cloning or fetching the system uses a JSON configuration file to keep track of the updates on the repository and to save a timestamp of the last time a repository has been updated. If there are no changes to a repository this event is emitted;
• git_guardian.pre_config_log_repository is emitted right before the information about the current repository are saved to the configuration file.

You can use the Gioffreda\Component\GitGuardian\Adapter\BitBucketRemote class to fetch the list of repositories owned by a specified user. If you provide the OAuth2 client ID and secret you can fetch the private ones as well. Here's an example on own to use the class:

<?php

use Gioffreda\Component\GitGuardian\Adapter\BitBucketRemote;

$bitBucketCredentials = [
    'client_id' => 'SbALNXBvnN_example',
    'client_secret' => '1JEfYU1n9mm6x4nYhkoC_example'
];

$remote = new BitBucketRemote();
$remote->setOptions($bitBucketCredentials);
$remote->setUser('acme');

You can listen to the discovery event of a repo to get the original raw definition fetched from the service by listening to the event git_remote.repository_discovery, for example to show a message in your console or to get more information about the repository than what you can get from the returned Gioffreda\Component\GitGuardian\Adapter\BitBucketRepository object.

<?php

use Gioffreda\Component\GitGuardian\Adapter\BitBucketRemote;

$remote = new BitBucketRemote();
$remote->setOptions([
    'client_id' => 'SbALNXBvnN_example',
    'client_secret' => '1JEfYU1n9mm6x4nYhkoC_example'
]);
$remote->setUser('acme');
$remote->getEmitter()->addListener('git_remote.repository_discovery', function ($event) {
    // do something with it
});

Available events emitted by the remote adapter are:

• git_remote.repository_discovery is emitted every time a repository is found and added to the list;
• git_remote.access_token is emitted only if you provided OAuth2 credentials, every time a new access token is received. It could be useful if you intend to use the access token to perform custom operation on your repositories;
• git_remote.client_request is emitted every time an API call is sent to the remote service and exposes the endpoint being called.

You can use the provided command bin/git-guardian to clone your repositories or list the known ones that you've already cloned locally. The command line interface is built using the Symfony Console Component and can be easily integrated in your Symfony project.

To clone all the repositories that belongs to a user, or users if you specify more than one you can use the built in command git:guardian:clone-all.

For example to clone locally your BitBucket repositories, including your private ones, run the built-in command like so:

$ ./bin/git-guardian git:guardian:clone-all \
    --client-id=SbAnN_example --client-secret=1JEfYU1nYhkoC_example \
    ggioffreda

This will clone all repositories of the given user locally. You can specify the destination directory. You can provide more than one username or team name and the below command will clone all repositories that belongs to those users or teams. This is an example:

$ ./bin/git-guardian git:guardian:clone-all \
    --client-id=SbAnN_example --client-secret=1JEfYU1nYhkoC_example \
    ggioffreda myorganisation mycompany myfriend

The command above will clone not only the public repositories for those users or teams, it will clone everything you have access to. If you do not provide the client ID and secret the command will clone only public repositories:

$ ./bin/git-guardian git:guardian:clone-all -v \
    ggioffreda myorganisation mycompany myfriend

The -v switch will ask for verbose output so you can see what's going on while the command runs.

Another example for cloning locally your GitHub repositories, including your private ones, is:

$ ./bin/git-guardian git:guardian:clone \
    --adapter=GitHub --personal-token=6a67fbb73cd_example \
    ggioffreda

The way GitHub authenticates is slightly different, so you have to provide your personal access token and your username as first user in the list of users/organisations you want to clone. This will clone all private repositories you have access to as well as the public ones for any other users you give on the command line. Since GitHub handles users and organisations differently you have to provide them as follows:

$ ./bin/git-guardian git:guardian:clone \
    --adapter=GitHub --personal-token=6a67fbb73cd_example \
    ggioffreda orgs/mycompany users/myfriend

You can clone just the public repositories without providing your personal access token, like so:

$ ./bin/git-guardian git:guardian:clone \
    --adapter=GitHub users/ggioffreda orgs/mycompany users/myfriend

Note that now your username requires to be identified as user and not organisation, otherwise the command will throw an error.

The help looks like below:

Usage:
  git:guardian:clone-all [options] [--] [<owner>]...

Arguments:
  owner                                The owner or owners of the repositories

Options:
      --adapter=ADAPTER                The adapter to use [default: "BitBucket"]
      --client-id=CLIENT-ID            The client ID (BitBucket only)
      --client-secret=CLIENT-SECRET    The client secret (BitBucket only)
      --personal-token=PERSONAL-TOKEN  The personal access token (GitHub only)
  -d, --destination=DESTINATION        The destination where to clone to [default: ".cloned"]
  -h, --help                           Display this help message
  -q, --quiet                          Do not output any message
  -V, --version                        Display this application version
      --ansi                           Force ANSI output
      --no-ansi                        Disable ANSI output
  -n, --no-interaction                 Do not ask any interactive question
  -v|vv|vvv, --verbose                 Increase the verbosity of messages: 1 for normal output, ...

Help:
 Fetches all the repositories for the given users

To list all known repositories you can run:

$ ./bin/git-guardian git:guardian:list-known

You can specify a different adapter, the destination where the repositories have been cloned and a different format. Available formats are:

• table (default) this format is useful for human analysis;
• table-borderless similar to the above but without vertical separators between columns;
• table-compact similar to table but with no borders
• csv prints the list in CSV format
• tsv prints the list in TSV format, basically a CSV using the tab character as separator
• json prints the list as a JSON object
• json-pretty prints the list as a JSON object, with indentation to enhance readability

Usage:
  git:guardian:list-known [options]

Options:
      --adapter=ADAPTER          The adapter to use [default: "BitBucket"]
  -d, --destination=DESTINATION  The destination where to clone to [default: ".cloned"]
  -F, --format=FORMAT            The format of the output [default: "table"]
  -h, --help                     Display this help message
  -q, --quiet                    Do not output any message
  -V, --version                  Display this application version
      --ansi                     Force ANSI output
      --no-ansi                  Disable ANSI output
  -n, --no-interaction           Do not ask any interactive question
  -v|vv|vvv, --verbose           Increase the verbosity of messages: 1 for normal output, ...

Help:
 List all known repositories

You can run the unit tests with the following command (requires phpunit):

$ cd path/to/Gioffreda/Component/Git/
$ composer.phar install
$ phpunit

This software is distributed under the following licenses: GNU GPL v2, GNU GPL v3 and MIT License. You may choose the one that best suits your needs.