mirror of https://github.com/FriendsOfTYPO3/tea.git synced 2024-11-23 04:36:13 +01:00
tea/Documentation/ContinuousIntegration.rst
Alexander Nitsche fc5b861bcd
[TASK] Update docs (#404)
See c2bb63bead for further details.

The README.md should mostly only cover the abstract and links.

The composer commands are the core value of this extension. List
all commands in the documentation and copy the descriptions from
the `composer.json`. This lets the global search at docs.typo3.org
find these commands.

Remove superfluous Linters page, which is integrated now in the
Running page.

Use sentence case in page titles in order to conform to the
TYPO3 documentation standards.

The ambiguous :ts: text role has been removed to
not confuse the writer with typescript and typoscript.

Add the common extension destinations to `composer.json`.
(Packagist displays them in a prominent place.)
2022-04-12 19:00:11 +02:00

1.6 KiB

Continuous integration

As an example, this extension provides several ways to perform the code quality checks and tests in a CI pipeline. You can copy the appropriate configuration depending on which Git hosting service and CI platform you want to use.

Table of Contents:

GitHub Actions

This extension has two code-checking workflows for GitHub Actions:

  • one that uses the local tools: This is the workflow you most probably would want to use: This workflow uses the development tools installed via Composer and PHIVE and calls them using the provided Composer scripts. Use this workflow if you want to run the code quality checks locally as well as in GitHub Actions.
  • one that completely relies on predefined actions: This workflow does not need the development tools to be installed locally. Use this workflow if you only want to run the code quality checks in GitHub Actions, but not locally.

GitLab CI

This extension also provides configuration for GitLab CI.