hivesolutions/Hive Deploy Action

Trigger a repository_dispatch event on a target repository

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit May 8, 2026
License: Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: hivesolutions/deploy-action@e47453a528827bc1226ff5481778618465876947 # v1.5.0

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

Inputs

name	description	required	default
repository	Target repository in 'owner/repo' format	yes	—
service	Service identity. Maps to the HCL file name (nomad/jobs/{group}/{service}.hcl). Use distinct service names for distinct deploys (e.g. 'mailog' vs 'mailog-latest').	no	—
group	Group (directory) the service belongs to (e.g. 'mail', 'apps'). Required when 'service' is provided.	no	—
tag	Image tag. When set, the receiving deploy workflow rewrites image lines in the HCL to this tag and bumps deploy_version. When omitted, only deploy_version is bumped.	no	—
channel	Deprecated. Accepted for backwards compatibility and passed through to client_payload, but no longer drives behavior. Use distinct 'service' names instead.	no	—
event-type	Value of the 'event_type' field for the repository_dispatch event. Defaults to 'deploy' when 'service' is provided. Required if 'service' is not provided.	no	—
client-payload	JSON string sent as 'client_payload'. Defaults to '{}'. Merged with any 'payload-*' keys and the auto-derived service/group/channel/tag (the latter take precedence).	no	{}
token	GitHub token (PAT) with 'repo' scope on the target repository	yes	—

Outputs

no outputs