Automate code migrations for TYPO3 Extensions
Daniel Siepmann
af8244f986
* As each node has to be handled differently. * Also we can attach many information for some nodes to the token, to make linting eaiser. But that's specific per node and those goes to an own class. Relates #67 |
||
---|---|---|
.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