Automate code migrations for TYPO3 Extensions
Daniel Siepmann
ded389aeca
* Use hash, not version, as version contains bug that not a single custom sniff can be executed. That would break our tests. * Also add auto loading for tests to work, as phpcs removed autoloading support for composer. * Move all sniffs to namespace to allow processing through phpcs. * Adjust already some class names of phpcs to new conventions. Relates: #82 |
||
---|---|---|
.gitlab/merge_request_templates | ||
Documentation | ||
src | ||
tests | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
composer.json | ||
LICENSE | ||
Makefile | ||
phpcs.xml.dist | ||
phpmd.xml | ||
phpunit.xml.dist | ||
Readme.rst |
About
Our goal is to provide an automated migration for TYPO3 updates.
This should include source code modifications like adjusting old legacy class names to new ones.
The official project home page can be found at https://git.higidi.com/Automated-TYPO3-Update/automated-typo3-update . Please open new issues and merge requests there. You can login with your Github account.
Github is just used as a mirror for the project.
Check out the official documentation at: https://automated-typo3-update.readthedocs.io