typo3-core-contributions

name

typo3-core-contributions

description

Use when contributing to TYPO3 Core — Forge issues, Gerrit patches, cherry-picks, CI debugging — or when working on **git.typo3.org**, the t3o site GitLab (`services/t3o-sites/**`: extensions.typo3.org/ter, common/t3olayout, anubis): merge requests, issues, work items, labels, pipelines. Core `main` is v15-in-progress (PHP 8.4/8.5); v14.3 LTS fixes land on branch `14.3` via cherry-pick. Triggers on: forge.typo3.org, review.typo3.org, git.typo3.org, t3o-sites, core patch, Gerrit review, TYPO3 Core contribution, TER website, t3olayout.

TYPO3 Core Contributions

When to Use — route by host

review.typo3.org (Gerrit), forge.typo3.org (Redmine), git.typo3.org/typo3/CI/cms (CI logs) are Core: Forge issues, patches, review, commit format, cherry-picks, rebasing — everything below. git.typo3.org/services/t3o-sites/** is plain GitLab for the t3o sites: no Gerrit, refs/for/main means nothing. Read references/t3o-gitlab-workflow.md first.

Prerequisites

Run ${CLAUDE_SKILL_DIR}/scripts/verify-prerequisites.sh: TYPO3.org account, Gerrit SSH (ssh -p 29418 <user>@review.typo3.org), Git email matching Gerrit.

Workflow

1. Setup: ${CLAUDE_SKILL_DIR}/scripts/setup-typo3-coredev.sh
2. Branch: git checkout -b feature/<issue>-description
3. Analyze: root cause, reproduction, affected versions first
4. Develop: fix + tests, validate with typo3-conformance-skill. Prove each test fails without the fix — references/proving-a-test.md
5. Commit: format below, Resolves: #<issue> +