GitHub Actions Compatibility

STACKIT Git Pipelines are compatible with the GitHub Actions workflow standard. This allows you to reuse existing workflows, actions, and automation patterns from the GitHub ecosystem.

Most workflows written for GitHub Actions can run on STACKIT Git Pipelines without modification.

Compatibility

STACKIT Git Pipelines support the GitHub Actions syntax for defining workflows and jobs.

This enables you to:

• Reuse existing GitHub Actions workflows
• Use public actions from the GitHub Marketplace
• Integrate commonly used automation tools

Marketplace Actions

You can reference public actions directly in your workflow configuration using the uses keyword.

Example:

steps:
  - name: Checkout repository
    uses: actions/checkout@v4

By default, actions are fetched from:

github.com

If required, the default action source can be changed through a STACKIT service request.

STACKIT Custom Actions

STACKIT will provide specialized actions designed to integrate with the STACKIT ecosystem.

These actions will simplify tasks such as:

• Authenticating with STACKIT services
• Accessing infrastructure resources
• Integrating with platform services

Details about available actions will be added as they become available.

Create and host custom actions

You can create your own reusable actions to share logic across multiple repositories or workflows.

Custom actions are stored in a Git repository and referenced from workflows.

1. Create a repository

Create a repository that will contain the custom action.

Example:

my-org/my-action

2. Define the action

Create an action.yml file in the repository to describe the action.

Example:

name: "My Custom Action"
description: "Does something useful"

inputs:
  who-to-greet:
    description: "Name of the person to greet"
    required: true
    default: "World"

runs:
  using: "node20"
  main: "index.js"

This file defines:

• The action name and description
• Input parameters
• The runtime environment
• The entry point of the action

3. Use the custom action in a workflow

Once the action is published, you can reference it from a workflow.

Example:

steps:
  - name: Run custom action
    uses: my-org/my-action@v1
    with:
      who-to-greet: "Developer"

The uses keyword specifies the repository and version of the action.

Next steps

After understanding GitHub Actions compatibility, you can explore additional topics:

• Configure pipelines and workflow syntax
• Use STACKIT managed runners
• Create custom runners for your infrastructure
• Integrate pipelines with STACKIT services