README

A slim, auto-synced, Drive-only subset of google/apiclient-services.

Unofficial. Not affiliated with, endorsed by, or supported by Google. See NOTICE.

Why

google/apiclient-services ships generated PHP classes for 200+ Google APIs in a single package — 200MB+ on disk — even if your project only ever talks to Google Drive. This package extracts just the Google\Service\Drive classes (~670 KB) and keeps them in sync with upstream automatically, on a weekly schedule, opening a pull request for review.

Install

composer require fojlerabbirabib/apiclient-drive-service google/apiclient

This package ships the Drive service classes; google/apiclient ships the Google\Client / HTTP / auth base layer they extend. This package provides google/apiclient-services and conflicts the real one, so Composer installs google/apiclient without the 200MB full service catalog — only the Drive classes ship.

Don't also require google/apiclient-services directly — it registers the same Google\Service\Drive namespace from a different file and Composer will refuse the combination. If you need other Google services, use google/apiclient-services instead of this package.

Usage

use Google\Client;
use Google\Service\Drive;

$client = new Client();
$client->setAuthConfig('/path/to/credentials.json');
$client->addScope(Drive::DRIVE_READONLY);

$drive = new Drive($client);
$files = $drive->files->listFiles();

How this stays up to date

A weekly GitHub Action pulls only the Drive-relevant files from upstream (via a scoped git sparse-checkout, not a full clone), runs the test suite and 95% coverage gate on the synced code, and opens a pull request for manual review — it never auto-tags or publishes. A daily staleness check fails loudly if the sync hasn't run successfully in 7 days.

BC checking is not automated. Roave/BackwardCompatibilityCheck could not resolve the google/apiclient base classes (this package only suggests them, and conflicts google/apiclient-services), so it emitted only spurious breaks. Review the sync PR's diff for breaking API surface before merging.

See CHANGELOG.md for the exact upstream commit each sync was based on.

Versioning

Standard SemVer, decided manually when a sync PR is merged:

License

Apache-2.0, same as upstream. See LICENSE and NOTICE.