Repository navigation
ripplemap 0.5.0: pull request comments
ripplemap maps the dependencies between the repos in your org from the files they already contain, so you can see what a change will affect before you merge it.
New: comments on pull requests
# .github/workflows/ripplemap.yml
name: ripplemap
on: pull_request_target
permissions:
contents: read
pull-requests: write
jobs:
impact:
runs-on: ubuntu-latest
steps:
- uses: Zintrivious/ripplemap@v0The Action comments with the repos a pull request may affect and keeps that comment up to date. Only the part of the repo that changed counts. Repos that pin nothing are flagged as getting the change on merge. It never checks out or runs the pull request's code. See the README for private orgs and inputs. The same analysis runs locally with ripplemap affected.
Also since the first release
- Scan a whole org without cloning:
ripplemap scan --org <name>, cached so repeat scans take a few API requests. ripplemap report: an interactive, self-contained HTML page with the impact graph and drift.- More formats: Kubernetes manifests, Helm charts,
go.mod, Python (pyproject.toml,requirements.txt), and workflow job containers and services. These join Dockerfiles, Terraform, GitHub Actions, npm and Compose. ripplemap unpinned: references to things your repos build that pin no version.- Never a silent partial graph: anything that couldn't be read is recorded and reported, and
--strictfails instead. - Tested on real orgs: linuxserver, sindresorhus, Cloud Posse, HashiCorp, Argo and Jupyter, with what each turned up fixed.
- Requires Node.js 22 or newer.
Install with npm install -g ripplemap or run with npx ripplemap.