Skip to content

Overview

Centralised reusable GitHub Actions workflows and shared GitHub App configurations, so downstream projects can avoid duplicating CI/CD boilerplate.

What's inside

  • Getting started

    How downstream repositories consume the reusable workflows and shared Probot configuration.

    Start here

  • Workflows

    Reusable GitHub Actions workflows for static tests, documentation, and releases.

    Workflow catalog

  • Probot

    Shared Probot configurations consumed via _extends: for settings, labelling, and release notes.

    Probot configurations

  • Portfolio App

    Centralised GitHub App that closes the GITHUB_TOKEN cascade gap. Works for organisations and personal accounts. Terraform module included.

    Setup

  • Development

    Local development setup: asdf, task, pre-commit, and running workflows with act.

    Contribute

How consumers reference this repository

jobs:
  static:
    uses: nolte/gh-plumbing/.github/workflows/reusable-pre-commit.yaml@develop

# .github/settings.yml
_extends: gh-plumbing:.github/commons-settings.yml

{
  "extends": ["github>nolte/gh-plumbing//renovate-configs/common"]
}

Pinning strategy

  • Reusable workflows: @develop for latest, @vX.Y.Z for reproducibility, @master for the latest published release.
  • Probot _extends: no pin possible—always resolves from the default branch (develop). See Probot → Settings → Versioning.
  • Renovate preset: append #vX.Y.Z (note: #, not @) to pin to a release tag.