fullsend-ai/Fullsend

Install fullsend-cli, create ${GITHUB_WORKSPACE}/output, invoke fullsend run with --output-dir pointing at that directory, then upload it with actions/upload-artifact. Does not read agent configuration from the repository; configure the job environment or CLI as needed.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 10, 2026
License
Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned
uses: fullsend-ai/fullsend@807037ff09a6b5d18fbc339d06e57752af9cd522 # v0.30.0

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

namedescriptionrequireddefault
agentAgent name passed to fullsend run (e.g. triage, code, review).yes
versionRelease tag or version: use latest, v0.0.1, or 0.0.1. Download URLs use a leading v; asset names use the version without v (fullsend_0.0.1_linux_amd64.tar.gz).latest
fullsend-dirPath to fullsend config directory (default GITHUB_WORKSPACE).""
target-repoPath to target repo checkout (default GITHUB_WORKSPACE/target-repo).""
github_tokenGitHub token for authenticated API calls (avoids 60 req/hour unauthenticated rate limit).${{ github.token }}
run-urlURL of the CI/CD run for status comments (optional).""
status-repoRepository (owner/repo) for status comments (optional).""
status-numberIssue/PR number for status comments (optional).""
mint-urlMint service URL for on-demand GitHub App tokens. Used for both status comment tokens and agent runtime tokens (GH_TOKEN, PUSH_TOKEN, REVIEW_TOKEN) minted by mintAgentToken().""
pr-head-shaPR head commit SHA, passed explicitly by per-repo (workflow_call) callers where GITHUB_EVENT_PATH lacks the dispatched event_payload wrapper. Takes precedence over GITHUB_EVENT_PATH extraction.""

no outputs