Download the PHP package owenbush/upkeep without Composer
On this page you can find all versions of the php package owenbush/upkeep. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download owenbush/upkeep
More information about owenbush/upkeep
Files in owenbush/upkeep
Package upkeep
Short Description Maintenance orchestrator CLI for contributed Drupal modules: cockpit-driven module registry, fixtures, and merge-request workflows.
License MIT
Informations about the package upkeep
Upkeep
Upkeep is a maintenance orchestrator CLI for contributed Drupal modules. From one "cockpit" directory it tracks every module you maintain across the Drupal core versions you support, shows every open contribution with its CI and local-check state on a single dashboard, runs each MR through a fully isolated check flow (PHPUnit, PHPStan, PHPCS, install, smoke) in a disposable per-module-per-core environment, and — for compat MRs that pass every gate — offers a human-approved fast-lane merge.
Environments are provisioned with ddev plus the ddev-drupal-contrib add-on (pinned at version 1.1.5) behind a thin adapter, and database fixtures come from the companion ddev-upkeep add-on. You never interact with either directly unless you want to.
Full documentation →
Quick start
Reading git.drupalcode.org needs no credential. A token is for writing: merging, commenting and publishing.
Documentation
Getting started
| Install | Requirements, installing, shell completion |
| GitLab token | What needs a credential and what does not |
| Set up a cockpit | The registry, and what lives in a cockpit directory |
| Base artifacts | The per-core building blocks, pre-release core majors, rebuilding |
| Publishing: issue forks and SSH | How work reaches drupal.org |
Daily flow
| The dashboard | Everything open, and what a row represents |
| Work on an issue | issues → start → publish |
| Patch contributions | The work a merge-request view cannot see |
| Running checks | The isolated flow, and how it matches drupal.org CI |
| Review, merge and release notes | Looking at it, merging it, writing it up |
| Working in an environment | A shell, a path, a running site |
| Fixtures | Check against real database state |
Reference
| Command reference | Every command, generated from the CLI itself |
| Exit codes | The 0/1/2 contract |
| Disk housekeeping | Where the space goes, and reclaiming it |
| Upgrading a cockpit | What a version change expects |
Design
| Design document | Why upkeep is shaped the way it is |
| The dashboard row model | Why a row is (module, issue, branch) |
| Any module, not just yours | The registry as a watchlist rather than a gate |
Policy stance
Merges are one human approval per merge request, by Drupal Association policy. There is deliberately no batch mode and no unattended merge path, and the browser UI deliberately has no merge button — a button that POSTs an action name is not the per-MR prompt that earns the approval. See Review, merge and release notes.
License
MIT — see LICENSE.
All versions of upkeep with dependencies
composer/semver Version ^3.4
symfony/console Version ^7.2 || ^8.0
symfony/http-client Version ^7.2 || ^8.0
symfony/process Version ^7.2 || ^8.0
symfony/yaml Version ^7.2 || ^8.0