guardian/guardian/actions-riff-raff

Build and upload Riff Raff artifacts.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 7, 2026
License
None

Pinned Snippet

workflow.ymlSHA-pinned
uses: guardian/actions-riff-raff@ab360a150e2540439f7f675c37d170a2fd6c8604 # v4.3.4

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
appRiff Raff app name. Either this or projectName should be set.no
roleArnRole to assume using AssumeRoleWithWebIdentity with Github OIDC token to upload files to RiffRaff S3 bucket.yes
configRiff Raff configuration (what would normally go in a riff-raff.yaml file). Use `|` to provide a multiline string here.no
configPathUse this to specify the path of a riff-raff.yaml file if you'd rather that than enter the config in your workflow file directly.no
projectNameDetermines Riffraff project name. Use this to override the default `stack::app` naming convention.no
dryRunIf set to true, logs the output but does not upload deployments to the Riff Raff S3 bucket.no
buildNumberIf set, will be used for the build number. (Typically this is read from process.env.GITHUB_RUN_NUMBER.)no
buildNumberOffsetIf set, will be added to the build number. (e.g. to offset builds to count from builds generated from a previous build tool)no
stagingDirUsed to set staging directory. You should not need to set this; it is intended for internal (testing) use only.no
contentDirectoriesA list of files/directories to upload to Riff-Raff. An alternative to nesting `sources` inside the `config` input.yes
githubTokenA GitHub token scoped to allow pull request commenting.yes
commentingStageWhen commenting on a pull request, which stage should be used. Typically a pre-production stage.noCODE
commentingEnabledWhether to comment on the pull request with Riff-Raff deployment links. See also `commentingStage`.notrue

no outputs