feat(action): dispatch/trigger - Trigger repository_dispatch events

Open
#39 0 comments 0 reactions 1 assignee View on GitHub

@aRustyDev is already working on this.

Since Jan 27, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement new-action

Parent Epic

Part of #22 (Atomic Release Pipeline Actions)

Priority

P1 - Core W2/W5 functionality for triggering downstream workflows

Description

Create a composite action that triggers repository_dispatch events to invoke other workflows.

Inputs

Input Required Default Description
event-type Yes - Event type to dispatch
client-payload No {} JSON payload to send
repository No github.repository Target repository
token No github.token GitHub token (needs repo scope)

Outputs

Output Description
dispatched "true" if successfully dispatched

Usage Example

- uses: arustydev/gha/actions/dispatch/trigger@v1
  with:
    event-type: "chart-pr-created"
    client-payload: '{"pr": 123, "artifact": "my-chart"}'

Implementation Notes

  • Uses GitHub API POST /repos/{owner}/{repo}/dispatches
  • Validates JSON payload before sending
  • Token must have repo scope for cross-repo dispatch

Source Reference

gha/.github/workflows/atomic-release-atomize-changes.yml:

  • Trigger validation workflow step (lines 404-418)
Dominant language
Shell
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/gh

All issues in aRustyDev/gh

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.