Cloud Installation
This page is for repository maintainers adding PRFlow’s optional GitHub Actions tier. Local plugin users do not need this installer.Prerequisites
Use a Git repository and run the installer from its root. Installgit before starting. A working Python 3.11 or newer is strongly recommended because the installer uses it to compare managed files and record their provenance.
Install From a Release Tag
-
Download the installer from the current release tag.
-
Read
devflow-install.shbefore running it. -
Run the downloaded file with the same tag in
DEVFLOW_REF. -
Review the result with
git statusandgit diff. - Commit only after the generated files and permissions match your repository policy.
DEVFLOW_REF select the same release tag. A tag is not an immutable byte pin. Use the same verified commit SHA in both places when immutability is required. Leaving DEVFLOW_REF unset selects the moving main branch.
Understand First-Install Behavior
A first installation applies immediately unless you pass--dry-run or set DEVFLOW_DRY_RUN=1. It creates or updates these public installation surfaces:
.github/workflows/devflow.ymlfor authorized comment commands..github/workflows/devflow-implement.ymlfor issue implementation..github/actions/read-project-config,.github/actions/setup-project-envand.github/actions/vendor-plugin..claude-plugin/marketplace.json..prflow/config.json,.prflow/config.schema.json,.prflow/.gitignoreand prompt-extension examples..prflow/install-manifest.json, when Python can record managed-artifact digests.- Repository ignore rules for installer sidecars.
devflow-review.yml, devflow-runner.yml or telemetry-push.yml. Automatic pull-request-triggered review is withdrawn from new installs. Use a collaborator’s /prflow:review comment instead.
Choose an Install Mode
The default is a thin install. The workflows fetch the plugin at runtime into.prflow/vendor/prflow/ using the pinned prflow_version. The fetched tree is ignored and is not committed.
Set DEVFLOW_VENDOR=1 to commit the plugin tree instead: