actions-marketplace-validations/Data transfer action

This action transfers data to/from artefact storage

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stalelast commit Dec 14, 2024
License
Public domain

Pinned Snippet

workflow.ymlSHA-pinned
uses: actions-marketplace-validations/reecetech_transfer-action@9c698ee18d76fc3bf46524c92b96128cdf1a26ae # no releases — HEAD as of 2026-07-10

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

namedescriptionrequireddefault
checkoutDo a Git checkout before transferring, either: `true` or `false`; defaults to `false`false
checkout-fetch-depthNumber of commits to fetch. 0 indicates all history for all branches and tags1
checkout-lfsWhether to download Git-LFS filesfalse
directionDirection of transfer, either: `upload` or `download`yes
if-no-files-foundThe desired behavior if no files are found using the provided path. Available Options: warn: Output a warning but do not fail the action error: Fail the action with an error message ignore: Do not output any warnings or errors, the action does not fail error
nameArtifact name: defaults to `checkout` if checkout input is `true`, otherwise, please provide a value
path⚠️ Conditional defaults! - if `checkout` is `true`; then defaults to `./.git/` - if `checkout` is `false`; then defaults to `./` Additionally, the meaning of `path` is: - if direction is `upload`: a file, directory or wildcard pattern that describes what to upload; - if direction is `download`: destination path
namedescription
nameArtifact name