releasetools/actions

Small, focused GitHub Actions for release pipelines. The current release is v0.0.6; use v0 to follow compatible updates on the current major line.

Actions

signed-push

Publish a local directory to a branch in any repository with a commit signed server-side by GitHub. It can replace the branch contents, update only the files you provide, and attach one or more lightweight tags to the resulting commit.

- uses: actions/create-github-app-token@v3
  id: app-token
  with:
    client-id: ${{ vars.RELEASE_APP_CLIENT_ID }}
    private-key: ${{ secrets.RELEASE_APP_PRIVATE_KEY }}
    owner: my-org
    repositories: my-target-repo

- uses: releasetools/actions/signed-push@v0
  with:
    source-dir: ./dist
    target-repo: my-org/my-target-repo
    headline: "publish: v1.2.3"
    tags: |
      v1.2.3
      v1
    force-tags: true
    token: ${{ steps.app-token.outputs.token }}

The action uses GitHub's createCommitOnBranch GraphQL mutation, so a GitHub App token produces a Verified commit without placing a private signing key on the runner. It also handles base64 file contents, race protection, pruning, and tag creation—the repetitive plumbing that otherwise ends up in every release workflow.

See the signed-push guide for mirroring, upserts, inputs, outputs, permissions, and behavior.

More actions are planned for common cross-workflow release patterns.

Development

See CONTRIBUTING.md for the repository layout, local development commands, and how action releases are assembled.

License

Apache 2.0. See LICENSE.