PatchRipple

Maintainer trial

Try PatchRipple on a pull request

The browser demo is available now. The consumer workflow below is ready to copy after the Action has a reviewed public release commit to pin.

The Action is not released yet. The downloadable workflow deliberately contains PATCHRIPPLE_COMMIT. Do not install it until that placeholder can be replaced with the reviewed full commit SHA of a published Action release.

Start with the demo

Explore the interactive synthetic report or read the technical walkthrough. The sample repository and commit IDs are fictional; the demo does not read a real repository.

Prepare the workflow

  1. Download the sample pull-request workflow. It uses pull_request, read-only contents: read permission, exact base/head SHAs, and an artifact upload step.
  2. After a release is published, replace only PATCHRIPPLE_COMMIT in the uses: line with that release's reviewed 40-character commit SHA. Keep the pinned SHA in place when upgrading.
  3. Save it as .github/workflows/patchripple.yml in a test repository. Open a pull request to run the analysis.
  4. In that run's GitHub Actions page, download the patchripple-<PR number> artifact, unzip it, and open index.html locally.
  5. Compare a few candidates with the actual changes. Record useful, missed, or misleading relationships and whether warnings were clear.
Download a sample bundle now: synthetic four-file offline report. It demonstrates the report format; it is not output from a real repository or a completed maintainer trial.

What to record

For a real trial, note the repository language/layout, exact tool commit, base and head SHAs, expected/missed/misleading edges, warning comprehension, whether the artifact opened, and whether it changed review focus. The report can expose repository paths and owner labels; share it only with the same care as the repository.

Use the maintainer trial thread for feedback, or inspect the source repository.