typo3-core-contributions

TYPO3 Core patches are submitted through Gerrit, which requires a Change-Id in your commit message, proper formatting per TYPO3 standards, and integration with the CI/CD pipeline. The workflow guides you through account setup, commit message rules, WIP state management, and patch iteration until acceptance.

TYPO3 Core enforces specific commit message standards including structured headers, footer tags, and Change-Id generation. This Skill covers the exact formatting rules and automated tools like git hooks to ensure compliance before submission to Gerrit.

CI/CD failures are caught by automated QA gates using phpstan, phpunit, and docker-based environments. This Skill explains how to run the same checks locally, interpret test output, fix issues, and resubmit patches without manual back-and-forth with reviewers.

Core contributions require composer for dependencies, git for version control, docker for isolated testing environments, phpstan for static analysis, phpunit for unit tests, and jq for JSON processing. This Skill verifies all prerequisites and automates setup through scripted workflows.

Yes, TYPO3 Core's Gerrit workflow supports WIP state to indicate patches under active development. This prevents premature review and signals your intention to iterate, and this Skill shows when and how to toggle WIP status during the contribution lifecycle.

Documentation and code contributions to TYPO3 Core both use the same Gerrit-based workflow, commit standards, and CI/CD checks. This Skill covers both contribution types, ensuring consistency across the project's submission and governance processes.