This repository holds reusable workflows for PMC's WordPress projects. These workflows are tailored to our specific needs and are not directly usable by other organizations, though they can provide a starting point for other organizations that maintain multiple WordPress themes and an accompanying set of plugins contained in a monorepo.
This composite action holds shared components for the reusable workflows found in this repository. Notably, reusable actions cannot reference files outside of the workflow file itself, so a composite action is used for shared scripts that would otherwise be included inline in each workflow file.
In the templates directory are example workflow files for the individual repositories that consume the reusable workflows. As needed, adjust the references for the secrets required by each workflow, as well as the inputs, to match the specific needs of the project.
stale-prs.yml marks PRs stale after 45 days
without activity and closes them 7 days later. PRs labeled keep-open are exempt.
When a PR closes this way, the first PUB-123 key in its branch name or title
gets the stale-pr-closed and exclude-from-productivity-report labels and a
comment linking the PR, then it is closed as Won't Do. The ticket is left
alone if it is already closed or another open PR still references it.
It runs as a dry run until the consuming repository sets the
STALE_PRS_LIVE variable to true. See the template.
Each run is capped by operations_per_run, so a large backlog is processed in batches.
A dry run labels, comments on, and closes nothing. Its job summary lists every PR
that would be closed and what would happen to its ticket. Dry runs don't save
progress between runs and use about 6 operations per PR, so raise
operations_per_run on a manual run to cover the whole backlog.