octoberswimmer/Flow2Apex PR Diff
Detect changed Salesforce Flow metadata files in a pull request, generate flow2apex old/new diffs, post them to the pull request, and optionally commit generated Apex files.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 30, 2026
- License
- None
Pinned Snippet
uses: octoberswimmer/flow2apex@f5ede0add01852891c82a290e0d88f38a9864f52 # v0.6.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| base-sha | Base commit SHA for the PR comparison. | yes | — |
| head-sha | Head commit SHA for the PR comparison. | yes | — |
| version | flow2apex release tag to install (for example `v0.2.0`). Use `latest` to resolve dynamically. | no | latest |
| release-repo | Repository that hosts flow2apex release assets (owner/name). Defaults to octoberswimmer/flow2apex. | no | octoberswimmer/flow2apex |
| github-token | Token for GitHub API calls and PR comments. Defaults to github.token when omitted. | no | "" |
| post-comment | Whether to upsert a PR comment with the generated diff report. | no | true |
| diff-format | Diff format for generated Apex output (`unified` or `side-by-side`). | no | unified |
| vitrine-url | Optional Vitrine base URL for viewing side-by-side HTML reports without downloading artifact ZIPs. | no | https://vitrine.octoberswimmer.com/ |
| commit-generated-apex-path | Optional repository-relative directory where generated Apex files should be written and committed. | no | "" |
Outputs
| name | description |
|---|---|
| has-flow-changes | Whether any `.flow` or `.flow-meta.xml` files changed in the PR. |
| comment-file | Path to the generated markdown report file. |
| html-file | Path to the generated side-by-side HTML report file when `diff-format` is `side-by-side`. |
| flow2apex-version | Resolved flow2apex release tag used for conversion. |