Laravel GitLab was created by, and is maintained by Graham Campbell, and is a GitLab PHP API Client bridge for Laravel. It utilises my Laravel Manager package. Feel free to check out the change log, releases, security policy, license, code of conduct, and contribution guidelines.
Laravel GitLab requires PHP 7.2-8.1. This particular version supports Laravel 6-9.
GitLab | L5.1 | L5.2 | L5.3 | L5.4 | L5.5 | L5.6 | L5.7 | L5.8 | L6 | L7 | L8 | L9 |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1.10 | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
2.7 | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ |
3.3 | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ |
4.4 | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ |
5.6 | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ |
To get the latest version, simply require the project using Composer. You will need to install any packages that "provide" psr/http-client-implementation
and psr/http-factory-implementation
. Most users will want:
$ composer require "graham-campbell/gitlab:^5.6" "guzzlehttp/guzzle:^7.4" "http-interop/http-factory-guzzle:^1.0"
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,
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:
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'
.
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"
.
This option ('cache'
) is where each of the cache configurations setup for your application. Only the "illuminate" driver is provided out of the box. Example configuration has been included.
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
.
This facade will dynamically pass static method calls to the 'gitlab'
object in the ioc container which by default is the GitLabManager
class.
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.
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/GitLabPHP/Client/tree/11.5.0#general-api-usage, and the manager class at https://github.com/GrahamCampbell/Laravel-Manager#usage.
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.
If you discover a security vulnerability within this package, please send an email to security@tidelift.com. All security vulnerabilities will be promptly addressed. You may view our full security policy here.
Laravel GitLab is licensed under The MIT License (MIT).
Available as part of the Tidelift Subscription
The maintainers of graham-campbell/gitlab
and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.