template-action

Template-action is a boilerplate repository for creating new GitHub Actions written in Go.

  • Development
  • Tools & Utilities
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

10/100 Low

Maintained
0last commit 1260 days ago
Popular
61 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM
GitHub stars
1
Open issues
7
Last commit
2023-06-10
License
Apache-2.0
Activity
stale

Checked 2 days ago - source: GitHub (mchmarny/template-action)

Resources & Compatibility

Minimum requirements: 8 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Using the template To create a new action, open the repository and click the green 'Use this Template' button, then follow the wizard to scaffold a new GitHub Action repository. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads