# template-action

template-action is a boilerplate repository for creating new GitHub Actions written in Go. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6045/template-action

## Description

Template-action is a boilerplate repository for creating new GitHub Actions written in Go. It pre-configures pull-request checks, Go and YAML linting, static analysis and vulnerability scanning, unit tests, release automation, and container image builds with SBOM signing and SLSA provenance, so developers can focus on writing action code instead of setting up CI from scratch.

## Platform availability

Available on 0 of 10 platforms.

## Health score

10/100 (Low), based on 4 of 4 factors.
- Maintained: 0 (last commit 1260 days ago)
- Popular: 6 (1 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 20 (8 GB minimum RAM, runs on ARM)

## Links

- GitHub: https://github.com/mchmarny/template-action
- Docker Hub: https://hub.docker.com/r/devopsinfra/template-action

## Common questions

### After using the template to create a new repository, what setup step is required before the workflow references my repo?

Clone the new repository and run tools/init in it. This updates the references to your newly created GitHub repository, so you should commit and push the changes.

### How do I trigger the release pipeline for a templated action?

Set the desired version in the .version file, commit and push that change if you edited it, then create and push a signed git tag for that version. You can also use make tag to automate the process.

### Where can I monitor the pipeline after pushing an initial commit or release tag?

Open the Actions page for the new repository and watch the triggered workflow jobs. If a job fails, open that job to see the cause and re-run by pushing fixes and a new tag for releases.

### Where is the built action image stored after a successful release?

The pipeline publishes the image to the repository's container packages, with the main image tagged by the release version. The signature and attestation OCI artifacts are also present and named by image digest.

### How can I verify provenance for the released image?

Each release image has an attached SLSA provenance attestation. You can query the image digest against a sigstore transparency service such as Rekor to inspect the recorded entry.

---
Source: Our Local Host (https://ourlocalhost.com/app/6045/template-action), the self-hosted and open-source app directory.
