--- title: Renaming the TYPO3 Github Repository url: "https://news.typo3.com/article/renaming-the-typo3-github-repository" description: "It's time for another cleanup of relics from times long past: The TYPO3 Core Team is changing the official repository name on GitHub from TYPO3/TYPO3.CMS to typo3/typo3." image: "https://news.typo3.com/_assets/d1e01514e4c4a5b3147940fa2ec50682/Images/og-image-news.jpg" date: 2026-06-11 modified: 2026-06-11 categories: - "Developer & Technology" - "Product Updates & Roadmap" --- # Renaming the TYPO3 Github Repository - [Developer & Technology](https://news.typo3.com/article/category/developer-technology) - [Product Updates & Roadmap](https://news.typo3.com/article/category/product-updates-roadmap) Renaming the TYPO3 Github Repository ==================================== 06 July 2021 ![](https://news.typo3.com/fileadmin/_processed_/8/f/csm_change-repository-name_d87fcf3c34.webp) It's time for another cleanup of relics from times long past: The TYPO3 Core Team is changing the official repository name on GitHub from TYPO3/TYPO3.CMS to typo3/typo3. - ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/860e9e538aa963a3600a2488dff48070.jpeg)[Benni Mack](https://news.typo3.com/article/author/benni-mack) The original naming scheme comes from a time where we had to distinguish between TYPO3 (the CMS) and the Flow/Neos packages. As time went by, the need for that distinction disappeared and our package-publishing mechanism has evolved: The main repository is now a [monorepo](https://en.wikipedia.org/wiki/Monorepo), which contains the TYPO3 Core and system extensions. The actual packages are split from this repository and published separately as a read-only repository. To avoid confusion for newcomers and align our naming scheme with other projects, we decided to rename our repository [typo3/typo3](https://decisions.typo3.org/t/renaming-of-github-repository/690). **Who Is Affected** ------------------- This change concerns you in any of the following cases: - You are an active core developer. - You cloned the TYPO3.CMS repository directly from GitHub. - You are using a reference to the GitHub repository in your projects. As GitHub will provide redirects for a while, projects and clones will not break immediately. However, GitHub will show a warning and you should use the new URLs. **Timeline** ------------ The change will come into effect on Monday, 19 July. **Changes for Core Developers** ------------------------------- We still use Gerrit for our review and quality assurance system, so nothing will change in the general workflow process for new patches. The current core development workflow has been using a git clone directly from git.typo3.org and a special *pushInsteadOf* config to push to Gerrit (the review system). ### **Before** The basic flow used to look like this: ``` git clone git://git.typo3.org/Packages/TYPO3.CMS.git . git config url."ssh://@review.typo3.org:29418".pushInsteadOf git://git.typo3.org git config remote.origin.push +refs/heads/master:refs/for/master ``` ### **After** The recommended—new—way of doing this is: ``` git clone https://github.com/typo3/typo3.git . git config remote.origin.pushurl "ssh://@review.typo3.org:29418/Packages/TYPO3.CMS.git" git config remote.origin.push +refs/heads/master:refs/for/master ``` **The first line changes cloning** from our own infrastructure on git.typo3.org to the new GitHub URL, as it is faster and maintained by GitHub. **The second line sets the remote pushUrl** to Gerrit—this way, the *pushInsteadOf* line is no longer needed. **The third line ensures that master pushes** are automatically rewritten to *refs/for/master,* the Gerrit-compatible way of publishing a patch for the master branch. The line can be repeated and adjusted for all other active branches (10.4 for example). ### **Additional Considerations** **If you have an existing *.gitconfig* file** for core development, make sure to change it accordingly: - Switch the origin to GitHub - Remove the pushInsteadOf config - Add the pushUrl config **We recommend cloning using SSH** for improved performance and security. **Help and Support** -------------------- If you have questions or run into problems with these changes, please let us know in the TYPO3 Slack [\#typo3-cms-coredev](https://typo3.slack.com/archives/C03AM9R17) channel. ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/d2f68d86720b93361f6910922465f559.jpeg) About the Author [Benni Mack](https://news.typo3.com/article/author/benni-mack) CTO at b13,Stuttgart, Germany [Website](https://b13.com/)[Twitter](https://twitter.com/bennimack)[LinkedIn](https://www.linkedin.com/in/benjaminmack/) Being the CTO at b13 GmbH, Benni is the TYPO3 Core Project Lead and one of the driving forces behind the TYPO3 community in the last years. [More posts by this author](https://news.typo3.com/article/author/benni-mack) Additional contributors ----------------------- - Proofreader - ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/d2606120ccc43c7846fe40337be2bc1e.png)Mathias Bolt Lesniak