[TASK] Migrate remaining repos to shared reusable workflows
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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.
Description
Context
The TYPO3-Documentation org is centralizing GitHub Actions workflows into shared reusable workflows in this repository. Initial PRs covered 4 repos:
- TYPO3CMS-Reference-CoreApi (#6414 closed — backport was migrated directly on
maininstead) - TYPO3CMS-Tutorial-Editors (#258 open — migrates backport + documentation to
@mainreferences) - TYPO3CMS-Tutorial-GettingStarted (#792 ✅ merged 2026-03-23)
- render-guides (#1196 open, approved)
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.
- TYPO3CMS-Reference-TCA — backport ✅ (
@46ed94f, current); still inline:test-documentation.yml,tests.yml,apply-precommit.yml - TYPO3CMS-Reference-Typoscript — backport ✅ (
@161f3be, stale pin); still inline:test-documentation.yml,tests.yml,apply-precommit.yml - TYPO3CMS-Reference-ViewHelper — backport ✅ (
@161f3be, stale pin); still inline:documentation.yml,tests.yml,apply-precommit.yml - TYPO3CMS-Tutorial-SitePackage — backport ✅ (
@161f3be, stale pin); still inline:documentation.yml,apply-precommit.yml(repo-specificauto-pr-sitepackage.ymlstays) - TYPO3CMS-Guide-FrontendLocalization — backport ✅ (
@161f3be, stale pin); still inline:test-documentation.yml,apply-precommit.yml - blog_example — still uses the broken
m-kuhn/backport@30b6e83onmain— the original urgent motivation for this initiative, and the last repo where it is unfixed onmain. Migration PR open: blog_example#188
Remaining work
- blog_example: migrate
backport.ymlto the shared workflow (urgent — currently broken). PR open: blog_example#188. - Migrate the remaining inline
test-documentation.yml/documentation.yml/tests.ymlworkflows in the five repos above. - Unify the reference style (
@mainvs 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 Dependabottarget-branchPRs now cover the maintained version branches of 10 repos (12.4/13.4/14.3; blog_example12.4/13.4— it has no14.3branch). - #15 adds
reusable-node-command.yml(first Node.js reusable; consumer: render-guidestheme-js-tests). - #16 adds a CI gate to this repository (actionlint, yamllint, zizmor, conformance) so
@mainconsumers can rely on merges here being validated.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TYPO3-Documentation/.github
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
TYPO3-Documentation/.github#7 · 1 comment ·
All issues in TYPO3-Documentation/.github
Similar issues
-
bot-found bug priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
madenvel/KalinkaPlayer#179 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
makeplane/helm-charts#332 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/fabric-cicd#1141 · 1 comment ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#3933 ·
Maintainers usually reply within 2 days
-
Remove CAAPFOpenkind/chore kind/cleanup needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rancher/turtles#2848 · 3 comments ·
Maintainers usually reply within 1 day