liquidlogiclabs/Trigger remote workflow (GitHub/Gitea)

Trigger a workflow in another repository on GitHub or Gitea (same or different instance).

Trust Signals

name	description	required	default
repo	Target repository. Formats supported: - owner/repo - https://github.com/owner/repo - https://gitea.example.com/owner/repo	no	—
workflow-name	Workflow name to dispatch. This is the top-level `name:` field in the workflow YAML file. If the workflow has no `name:` field, the filename (without extension) is used as fallback. NOT the job name or step name. Example: if your workflow has `name: CI/CD Pipeline`, use `workflow-name: CI/CD Pipeline`. Example: if your workflow file is `build.yml` with no name field, use `workflow-name: build`.	yes	—
ref	Git ref to run the workflow on (branch/tag/SHA).	no	main
base-url	Base URL for the target instance (GitHub or Gitea). Auto-inferred from repo URL or runner env (GITHUB_SERVER_URL / GITEA_SERVER_URL). Override if inference is incorrect.	no	—
token	API token for the target instance (GitHub or Gitea). If omitted, falls back to runner environment token (GITHUB_TOKEN or GITEA_TOKEN). Token must have permission to read workflows and dispatch runs in the target repo.	no	—
inputs	Optional JSON object string of inputs for the workflow dispatch.	no	—
skip-certificate-check	Skip TLS certificate verification for API calls (self-hosted instances).	no	false
verbose	Enable verbose logging (HTTP attempts, endpoint discovery, response snippets). Also enabled when ACTIONS_STEP_DEBUG=true.	no	false

name	description
status	HTTP status code returned by the dispatch request (typically 204 on GitHub, 201/204 on Gitea).
endpoint	The API endpoint URL used to dispatch the workflow. Useful for debugging platform/instance routing.