- Dec 15, 2020
-
-
Christian Kuhn authored
Travis CI for core has been flaky for a while - processes tend to die or are queued forever. The only thing travis still executed for us is updating sonar cloud data. This service has been introduced some years ago but did never find significant usage and has never been configured. The patch drops travis along with sonar-cloud. If anyone wants to pick up work with sonar again, it could be added as github action again. Change-Id: I2929bfb1f72d1a6af273692b4f632d90280bf074 Resolves: #93084 Releases: master, 10.4, 9.5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67144 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
- May 22, 2020
-
-
Benjamin Franzke authored
Git converts CRLF to LF when plaintext files are staged. The existing copies of the rte_ckeditor Contrib/* sources have therefore already been converted to LF by git [1]. Initially these files had been copied as CRLF from the ckeditor4 sources in node_modules by grunt npmcopy. Now, when `yarn build` is executed, the copy operation is performed again, which means the files are reverted back to CRLF. Git therefore needs to perform the CRLF to LF conversion again. (Which itself needs to be triggered by the developer by staging the changed files) We do now mimic git`s autocrlf behaviour and replace CRLF by LF in the files copied from ckeditor Contrib/* folders to prevent the files from clobbering the `git status` or `git diff` output. By passing `encoding: null` to the grunt.file.copy options we ensure that binary files will be copied as is. Also configure *.svg files to be checked out as LF on all platforms (namely windows) like we do for other plaintext files as well. This ensures svg files do not show up (in windows) as changed because their original from node_modules was stored as LF. *.patch is added as patching jquery on windows would fail otherwise. [1] https://git-scm.com/docs/gitattributes#_end_of_line_conversion Resolves: #91374 Releases: master, 9.5 Change-Id: I2977a6d44f96f6593152bfe698ba5d35f32b131f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64481 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
-
- Mar 20, 2020
-
-
Alexander Schnitzler authored
This patch simply pulls out the level 2 rules into a separate configuration file which is a copy of the original level 2 configuration file of phpstan with some rules, services and parameters disabled. Also, additional configuration files are put into the Build folder and phpstan.neon has been added to the .gitattributes file. Releases: master Resolves: #90789 Change-Id: Ia3b3c30cfa57227c0607904df38add31f36be0e2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63802 Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
-
- Nov 27, 2019
-
-
Alexander Schnitzler authored
composer require --dev rector/rector:"^0.5.0" This commit introduces the requirement to rector/rector to automatically process code changes by given set of rules. To make this commit more meaningful, a first set "php53" has been processed. Releases: master Resolves: #89785 Change-Id: I6e2ff9654266458ae9fb6800547ff4712b0b66d8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62437 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
- Oct 02, 2019
-
-
Georg Ringer authored
Crowdin requires a basic configuration which defines where the XLIFF files and their translations are located. The configuration is used by the GitHub integration which is offered by Crowdin itself. See https://support.crowdin.com/github-integration/ for more information about that. Even though the translations will not be pushed back to the GitHub repository of TYPO3 (as pull requests), the "translation" property is required as the manual export of translations will use it. Resolves: #89281 Releases: master, 9.5 Change-Id: I1a5f94b416a0652081976bcdbd9ea7d61fb202dc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61846 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
-
- Oct 28, 2018
-
-
Christian Kuhn authored
Resolves: #86774 Releases: master, 8.7 Change-Id: I8b677426c6011a0b3115f83380ae567582dc9c17 Reviewed-on: https://review.typo3.org/58747 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
- Jul 29, 2018
-
-
Andreas Fernandez authored
Since the TypeScript sources don't have any impact on the behavior of the application and are just meant for development purpose, it's safe to exclude these files in the packaging process. Resolves: #85674 Releases: master Change-Id: I599433d68834a3424e5cf7d77612d2478d46510e Reviewed-on: https://review.typo3.org/57713 Tested-by:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
-
- Sep 08, 2017
-
-
Benjamin Kott authored
Resolves: #82392 Releases: master, 8.7 Change-Id: I2ba42454a6b16aa8b4dd97a5741251b4fe265c0e Reviewed-on: https://review.typo3.org/54039 Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
-
- May 17, 2017
-
-
Andreas Allacher authored
The new file extension .typoscript will be the default for TypoScript configuration files and is the only recommended one from now on. This effort is made to introduce a dedicated file extension for TypoScript configuration files, and to avoid conflicts with already existing and more spread file extensions like ".ts" for TypeScript or Video Transport Stream Files. Resolves: #78161 Resolves: #80689 Releases: master, 8.7 Change-Id: I44b41631f498e3ba39e0f1936329094a59859f4e Reviewed-on: https://review.typo3.org/50096 Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
- Mar 26, 2017
-
-
Benjamin Kott authored
In preparation for upcomming switch from bootstrap to SASS the backend style sources have been migrated to SASS. The autoprefixer configuration was corrected to match CMS8 LTS requirements and minification of CSS files is now enabled. Automatic style checks are now available through grunt. The tasks `grunt format` and `grunt lint` will now check sources files for consistency. Resolves: #80453 Releases: master Change-Id: I9ba23aea78014a1f0cce229db533a81d5ffcd02f Reviewed-on: https://review.typo3.org/52151 Tested-by:
Marco Christian Krenn <krenn@webconsulting.at> Tested-by:
-
- Feb 14, 2017
-
-
Susanne Moog authored
As the testing framework shall be a standalone component which will be required via composer it has been excluded from the exported files via .gitattributes. Change-Id: I74708a31b3848105a949268e9caa1160c59cbc30 Resolves: #79783 Releases: master Reviewed-on: https://review.typo3.org/51659 Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
- Dec 02, 2016
-
-
Kay Strobach authored
This settings enforces LF consistently on all plattforms and fits it to the .editorconfig Resolves: #77808 Releases: master, 7.6, 6.2 Change-Id: Ibc6efbf9a2a2360d84aa0ed4c3b74ff731ef1398 Reviewed-on: https://review.typo3.org/49791 Tested-by:
Jan Helke <typo3@helke.de> Tested-by:
-
- Jun 03, 2016
-
-
Helmut Hummel authored
To ease the usage of the core with extensions, we move the base test classes into a different place to be able to make them available when typo3/cms is pulled in as dependency, e.g. for testing extensions or in projects. This is a non breaking change, as the classes will be available in any case after that. By doing so, we can nicely cleanup the .gitattributes file Resolves: #76425 Releases: master Change-Id: I639f08a4e3e5dd73aa47570d326b72c64452acaf Reviewed-on: https://review.typo3.org/48428 Reviewed-by:
Elmar Hinz <t3elmar@gmail.com> Reviewed-by:
-
- Jun 01, 2016
-
-
Mathias Brodala authored
This excludes various directories and files from release archives as generated by Github and fetched via Composer. These files and directories are not relevant for production and excluding them reduces the size of release archives. Such files are usually identified as security risk in security reviews and should therefore be removed by default from production systems. As an addition it also avoids issues with long file paths when installing on Windows systems. Resolves: #65570 Resolves: #68998 Resolves: #70810 Releases: 7.6, master Change-Id: I615e0c7a4cafaea471c79e88e9df2c78c55b92ac Reviewed-on: https://review.typo3.org/46357 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Mathias Schreiber <mathias.schreiber@wmdb.de> Tested-by:
Helmut Hummel <helmut.hummel@typo3.org> Tested-by:
-
