Skip to content

Drupal contrib maintenance, from the terminal

Every open issue, merge request and patch across every Drupal module you maintain: triaged, checked in a disposable environment, and merged one deliberate approval at a time. One static binary, no runtime to install.
Terminal window
brew install owenbush/tap/upkeep

macOS and Linux, amd64 and arm64. No PHP and no Composer. The binary is static, signed and notarized. Prefer Go, or no Homebrew?

Terminal window
go install github.com/owenbush/upkeep/cmd/upkeep@latest

Or take an archive from the releases page. It drives ddev, which you will want. Full options, including shell completion, are in Install.

Recorded against real modules in a real cockpit, at a pace you can actually read.

Maintaining a contributed Drupal module is mostly triage, and the triage is the expensive part. A mature project carries a hundred open merge requests, sixty issues with patches attached, and a Project Update Bot compatibility branch waiting on every new core release. Working out which of those is actually ready costs more than reviewing the one that is.

So the work piles up, not because the fixes are hard, but because finding the ready ones means a browser, a dozen tabs, and a local site you daren’t break.

The next core version just landed

Project Update Bot opens a compatibility merge request on every module you maintain. Check all of them against the new core in disposable environments, then merge the green ones, each with its own deliberate yes.

Base artifacts for a pre-release core major are a supported, deliberate build, because that is when compatibility work actually happens.

Green locally, red on CI

drupal.org does not test the contributor’s branch. It tests that branch merged into the current tip of the target. Measured on pathauto: 23 of 25 open merge requests have a merge tree that differs from their branch, some of them 41 commits behind.

Upkeep checks the same tree CI does, so a local pass means something.

Half the contributions aren't merge requests

Patches posted to an issue are invisible to a merge-request view, and plenty of real work arrives that way. Upkeep finds them, applies one against the branch its issue was filed against, and can promote it onto a work branch credited to the person who posted it.

Somebody's MR needs finishing

A bot MR that stopped short of the info.yml change, or a contribution that went quiet. upkeep checkout puts your working copy on its actual source branch, adds the remote to push back to, and tells you the command that sends it.

Your module needs more than an empty site

A module that manages vocabulary terms cannot be tested without terms. Capture the state once as a sanitised, committed fixture and check against it every time, including the other contrib it needs, installed automatically wherever it is loaded.

The issue queue moved to GitLab

drupal.org is migrating issue queues, one project at a time. Upkeep asks each project where its issues live and reads whichever queue is the live one, so a migrated project keeps working, including issues that have no drupal.org node at all.

Two tiers, because volume is real. Start wide:

MODULE BRANCHES MRS PATCH ISSUES READY CI FAILED UNCHECKED CACHED
pathauto 8.x-1.x 100 22 – 2 118 17h ago
paragraphs 1.0.x,2.0.x 12 61 2 1 71 2m ago

Then name a module, and every row says what it is in plain English and the command to run next:

MODULE ISSUE VERSION TITLE MR PATCH CI LOCAL STATUS NEXT
pathauto 3262847 review 8.x-1.x Only update child taxo… !12 – – – needs a check upkeep check pathauto 12 --version=10
pathauto 3608383 RTBC 8.x-1.x Remove forum integratio !99 – pass pass 10,11 ready to merge upkeep merge --fast-lane
pathauto 3311669 review 8.x-1.x Punctuation processed… !40 +1 2 ↑ fail fail 10 CI failed upkeep check pathauto 40 --version=10
pathauto 3597857 active 8.x-1.x Config schema for form – 4 – stale 11 4 patches upkeep patch:check pathauto 3597857

Every row yields a command. You never have to work out what to do with one.

What a row represents →

The fast lane finds the merge requests that cleared every gate, usually bot compatibility work, and then asks you about each one, individually, before merging it.

There is deliberately no batch mode and no unattended merge path. That is Drupal Association policy, and it is asserted structurally in the test suite rather than left to good intentions.