Migrate Travis CI to GitHub Actions

Author: battye

.github/workflows/phpunit.yaml

@@ -0,0 +1,29 @@
+# .github/workflows/phpunit.yaml
+name: phpunit
+
+on: [push, pull_request]
+
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        php: ['5.6', '7.0', '7.1']
+
+    name: PHP ${{ matrix.php }} tests
+    steps:
+      - run: echo "This job for ${{ github.ref }} was automatically triggered by a ${{ github.event_name }} event on ${{ runner.os }}."
+
+      # Basically git clone
+      - uses: actions/checkout@v2
+
+      # Use PHP of specific version
+      - uses: shivammathur/setup-php@v2
+        with:
+          php-version: ${{ matrix.php }}
+          coverage: none # disable xdebug, pcov
+
+      # If we use two steps like this, we can better see if composer or the test failed
+      - run: composer install --dev --no-interaction --prefer-source
+      - run: vendor/phpunit/phpunit/phpunit
+      - run: echo "This job's status is ${{ job.status }}."

.travis.yml

@@ -37,19 +37,19 @@ The `--safe-mode` flag indicates that you want to parse files instead of directl
 
 ## Tests
 
-[![Build Status](https://travis-ci.org/phpbb/phpbb-translation-validator.png?branch=master)](https://travis-ci.org/phpbb/phpbb-translation-validator)
+![GitHub Actions CI](https://github.com/phpbb/phpbb-translation-validator/actions/workflows/phpunit.yaml/badge.svg?branch=master)
 
-Add the TranslationValidator as a dependency:
+In your project you can add phpBB Translation Validator as a dependency:
 
 		{
 			"require-dev": {
 				"phpbb/translation-validator": "1.5.*"
 			}
 		}
 
-Then add a `php vendor/bin/translation.php` call to your `.travis.yml` file.
+Then add a `php vendor/bin/translation.php` call to your workflow.
 
-We use Travis-CI as a continuous integration server and phpunit for our unit testing. See more information on the [phpBB development wiki](https://wiki.phpbb.com/Unit_Tests).
+We use GitHub Actions as a continuous integration server and phpunit for our unit testing.
 
 To run the unit tests locally, use this command: