A curated set of composite actions for integration, release, and repo automation. Reference them from your workflow in a single line. No bash scaffolding, no glue code.
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: elpic/actions/integration/go/test@v1Each action ships a single action.yml. Drop it into any job and it handles checkout and tooling internally.
Pin to v1, v1.2, or v1.2.3. Floating major tags move forward, immutable point releases stay put.
Lint, test, and security jobs ship as separate steps so you can compose the pipeline that fits your repo.
You define runs-on, triggers, and job graph. The actions do the rest. No bash scaffolding required.
/ categories
PR integration: test, lint, build, security
Release and publish to registries
GitHub-specific composite actions
General-purpose composite actions
/ usage
Every action is a composite action with its own action.yml. You control runs-on, triggers, and job dependencies. Each action handles its own checkout and tooling setup internally.
name: PR
on: [pull_request]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: elpic/actions/integration/python/lint@v1
test:
runs-on: ubuntu-latest
steps:
- uses: elpic/actions/integration/python/test@v1
security:
runs-on: ubuntu-latest
steps:
- uses: elpic/actions/integration/python/security@v1/ versioning
Floating major
Latest v1.x release. Moves forward with non-breaking changes.
Floating minor
Latest v1.2.x patch. Bug fixes only inside this minor line.
Immutable
Exact point-in-time release. Never moves. Maximum reproducibility.
Blueprint-rendered templates for Dockerfiles and GitHub Actions workflows. Declare versions once, render every file, and detect drift automatically in CI.
Visit elpic/templatesOpen the repo, copy a single uses: line, and your workflow is wired up.
Open elpic/actions