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.
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.
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.
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.