TYPO3-Documentation / TYPO3-Documentation/.github

[TASK] Migrate remaining repos to shared reusable workflows

Open
#5 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Context

The TYPO3-Documentation org is centralizing GitHub Actions workflows into shared reusable workflows in this repository. Initial PRs covered 4 repos:

Status update (2026-07-04)

The backport migration has since happened in 5 of the 6 repos below — but via per-repo SHA pins instead of @main, and the pins have already drifted (most repos pin 161f3be, one commit behind current main = 46ed94f, missing the backport success/failure labels fix). This is exactly the per-repo maintenance burden ADR-003 (#6) proposes to eliminate.

Remaining work

  1. blog_example: migrate backport.yml to the shared workflow (urgent — currently broken). PR open: blog_example#188.
  2. Migrate the remaining inline test-documentation.yml / documentation.yml / tests.yml workflows in the five repos above.
  3. Unify the reference style (@main vs SHA pin) once ADR-003 (#6) is decided; the June SHA-pin migrations have already produced drift.

The current workflow inventory is documented in this repo's README.

Migration pattern

For each repo, replace inline workflow files with shared workflow calls:

# Before (inline)
jobs:
  backport:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@...
      - uses: m-kuhn/backport@30b6e83  # BROKEN

# After (shared)
jobs:
  backport:
    uses: TYPO3-Documentation/.github/.github/workflows/reusable-backport.yml@main

Related work since this issue was filed

  • Version-branch drift (workflow bumps only land on main, maintained branches never get them) was root-caused via FrontendLocalization#136 / #137; per-repo Dependabot target-branch PRs now cover the maintained version branches of 10 repos (12.4/13.4/14.3; blog_example 12.4/13.4 — it has no 14.3 branch).
  • #15 adds reusable-node-command.yml (first Node.js reusable; consumer: render-guides theme-js-tests).
  • #16 adds a CI gate to this repository (actionlint, yamllint, zizmor, conformance) so @main consumers can rely on merges here being validated.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the workflow inventory in the repository README and compare the listed repositories' inline workflow files: test-documentation.yml, documentation.yml, tests.yml, apply-precommit.yml, and blog_example's backport.yml. Review the open blog_example#188 migration and the reusable workflow files in this repository. Done means the remaining workflows use the shared calls, while the repo-specific auto-pr-sitepackage.yml remains in place.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.