GrahamCampbell / Laravel-GitLab by graham-campbell

GitLab Is A GitLab Bridge For Laravel
435,983
137
6
Package Data
Maintainer Username: graham-campbell
Maintainer Contact: hello@gjcampbell.co.uk (Graham Campbell)
Package Create Date: 2018-03-03
Package Last Update: 2024-03-17
Home Page: https://gjcampbell.co.uk
Language: PHP
License: MIT
Last Refreshed: 2024-12-23 03:00:11
Package Statistics
Total Downloads: 435,983
Monthly Downloads: 9,074
Daily Downloads: 33
Total Stars: 137
Total Watchers: 6
Total Forks: 28
Total Open Issues: 3

Laravel GitLab

Laravel GitLab was created by, and is maintained by Graham Campbell, and is a PHP GitLab API bridge for Laravel 5. It utilises my Laravel Manager package. Feel free to check out the change log, releases, license, and contribution guidelines.

Installation

Laravel GitLab requires PHP 7.1 - 7.3. This particular version supports Laravel 5.5 - 5.8 only.

To get the latest version, simply require the project using Composer. You will need to install any package that "provides" php-http/client-implementation. Most users will want:

$ composer require graham-campbell/gitlab php-http/guzzle6-adapter:^1.1

Once installed, if you are not using automatic package discovery, then you need to register the GrahamCampbell\GitLab\GitLabServiceProvider service provider in your config/app.php.

You can also optionally alias our facade:

        'GitLab' => GrahamCampbell\GitLab\Facades\GitLab::class,

Configuration

Laravel GitLab requires connection configuration.

To get started, you'll need to publish all vendor assets:

$ php artisan vendor:publish

This will create a config/gitlab.php file in your app that you can modify to set your configuration. Also, make sure you check for changes to the original config file in this package between releases.

There are two config options:

Default Connection Name

This option ('default') is where you may specify which of the connections below you wish to use as your default connection for all work. Of course, you may use many connections at once using the manager class. The default value for this setting is 'main'.

GitLab Connections

This option ('connections') is where each of the connections are setup for your application. Example configuration has been included, but you may add as many connections as you would like. Note that the 3 supported authentication methods are: "none", "oauth", and "token".

Usage

GitLabManager

This is the class of most interest. It is bound to the ioc container as 'gitlab' and can be accessed using the Facades\GitLab facade. This class implements the ManagerInterface by extending AbstractManager. The interface and abstract class are both part of my Laravel Manager package, so you may want to go and checkout the docs for how to use the manager class over at that repo. Note that the connection class returned will always be an instance of \Gitlab\Client.

Facades\GitLab

This facade will dynamically pass static method calls to the 'gitlab' object in the ioc container which by default is the GitLabManager class.

GitLabServiceProvider

This class contains no public methods of interest. This class should be added to the providers array in config/app.php. This class will setup ioc bindings.

Real Examples

Here you can see an example of just how simple this package is to use. Out of the box, the default adapter is main. After you enter your authentication details in the config file, it will just work:

use GrahamCampbell\GitLab\Facades\GitLab;
// you can alias this in config/app.php if you like

GitLab::groups()->all();
// we're done here - how easy was that, it just works!

The gitlab manager will behave like it is a \Gitlab\Client class. If you want to call specific connections, you can do with the connection method:

use GrahamCampbell\GitLab\Facades\GitLab;

// writing this:
GitLab::connection('main')->groups()->all();

// is identical to writing this:
GitLab::groups()->all();

// and is also identical to writing this:
GitLab::connection()->groups()->all();

// this is because the main connection is configured to be the default
GitLab::getDefaultConnection(); // this will return main

// we can change the default connection
GitLab::setDefaultConnection('alternative'); // the default is now alternative

If you prefer to use dependency injection over facades like me, then you can easily inject the manager like so:

use GrahamCampbell\GitLab\GitLabManager;
use Illuminate\Support\Facades\App; // you probably have this aliased already

class Foo
{
    protected $gitlab;

    public function __construct(GitLabManager $gitlab)
    {
        $this->gitlab = $gitlab;
    }

    public function bar()
    {
        $this->gitlab->groups()->all();
    }
}

App::make('Foo')->bar();

For more information on how to use the \Gitlab\Client class we are calling behind the scenes here, check out the docs at https://github.com/m4tthumphrey/php-gitlab-api, and the manager class at https://github.com/GrahamCampbell/Laravel-Manager#usage.

Further Information

There are other classes in this package that are not documented here. This is because they are not intended for public use and are used internally by this package.

Security

If you discover a security vulnerability within this package, please send an e-mail to Graham Campbell at graham@alt-three.com. All security vulnerabilities will be promptly addressed.

License

Laravel GitLab is licensed under The MIT License (MIT).