Shared Forgejo Actions
Find a file
2026-04-30 14:30:02 +02:00
.forgejo/workflows fix: update runner environment to stackit-ubuntu-22 2026-04-30 10:13:34 +02:00
aikido-full-scan fix: correct paths 2026-04-30 13:17:44 +02:00
aikido-pr-scan fix: correct paths 2026-04-30 13:17:44 +02:00
aws-configure ci: add codeowners 2026-04-24 16:05:57 +02:00
checkout fix: correct paths 2026-04-30 13:17:44 +02:00
internal-aikido-full-scan feat: add Aikido full and PR scan actions 2026-04-30 13:17:44 +02:00
internal-aikido-pr-scan feat: add Aikido full and PR scan actions 2026-04-30 13:17:44 +02:00
pnpm-build feat: add pnpm-build action 2026-04-30 14:02:09 +02:00
publish-static-contents feat: add publish-static-contents action 2026-04-30 14:02:09 +02:00
terraform-validate feat: add terraform-validate action 2026-04-30 14:30:02 +02:00
CODEOWNERS ci: add codeowners 2026-04-24 16:05:57 +02:00
README.md feat: add terraform-validate action 2026-04-30 14:30:02 +02:00

shared-actions

Shared actions for Forgejo CI/CD pipelines.

Actions

Action Description
aikido-full-scan Aikido full scan
aikido-pr-scan Aikido PR scan
aws-configure Authenticate with AWS via OIDC
checkout Action for checking out a repository
pnpm-build Action for building and validating with PNPM
publish-static-contents Syncs frontend assets to S3 and invalidates a CloudFront distribution
terraform-validate Validate Terraform configuration files using the official Terraform CLI

Security

Where third-party Forgejo/GitHub Actions are used internally, they are pinned to exact commit hashes rather than mutable tags to prevent supply chain attacks.

Usage

Reference actions from your project's workflow:

- uses: https://schmalz-git.git.onstackit.cloud/schmalz/shared-actions/<action-name>@<action-name>-v1
  with:
    # see each action's README for inputs

Each action has its own README with inputs, usage examples, and notes.