Merge pull request #814 from alleyinteractive/fix/github-tests

Move CI to GitHub Actions

Author: dlh01

.github/workflows/phpcs.yml

@@ -0,0 +1,56 @@
+name: PHPCS
+
+on:
+  pull_request:
+
+jobs:
+  coding-standards:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: true
+
+    name: Coding Standards
+    steps:
+      - name: Cancel previous runs of this workflow (pull requests only)
+        if: ${{ github.event_name == 'pull_request' }}
+        uses: styfle/cancel-workflow-action@0.5.0
+        with:
+          access_token: ${{ github.token }}
+
+      - name: Check out code
+        uses: actions/checkout@v2
+
+      - name: Get Composer cache directory
+        id: composer-cache
+        run: echo "::set-output name=dir::$(composer config cache-files-dir)"
+
+      - name: Set up Composer caching
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-composer-dependencies
+        with:
+          path: ${{ steps.composer-cache.outputs.dir }}
+          key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-composer-
+
+      - name: Set up PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: '7.4'
+          extensions: dom, curl, libxml, mbstring, zip, pcntl, pdo, sqlite, pdo_sqlite, gd
+          tools: composer:v2
+          coverage: none
+
+      - name: Validate Composer config
+        run: composer validate --strict
+
+      - name: Install composer dependencies
+        uses: nick-invision/retry@v1
+        with:
+          timeout_minutes: 5
+          max_attempts: 5
+          command: composer install
+
+      - name: Run PHPCS
+        run: composer run phpcs -- -v

.github/workflows/phpunit.yml

@@ -0,0 +1,85 @@
+name: PHPUnit
+
+on:
+  pull_request:
+
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+
+    services:
+      mysql:
+        image: mysql:5.7
+        env:
+          MYSQL_ALLOW_EMPTY_PASSWORD: yes
+        ports:
+          - 3306:3306
+        options: --health-cmd="mysqladmin ping" --health-interval=10s --health-timeout=5s --health-retries=3
+    continue-on-error: ${{ matrix.can_fail }}
+    strategy:
+      fail-fast: true
+      matrix:
+        php: [8.0, 7.4, 5.6]
+        wp_version: ["latest"]
+        can_fail: [false]
+        multisite: [0,1]
+
+    name: WordPress ${{ matrix.wp_version }} @ PHP ${{ matrix.php }} (WP_MULTISITE=${{ matrix.multisite }})
+    env:
+      CACHEDIR: /tmp/test-cache
+      WP_CORE_DIR: /tmp/wordpress/
+      WP_TESTS_DIR: /tmp/wordpress-tests-lib
+      WP_VERSION: ${{ matrix.wp_version }}
+      WP_MULTISITE: ${{ matrix.multisite }}
+
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v2
+
+      - name: Get Composer cache directory
+        id: composer-cache
+        run: echo "::set-output name=dir::$(composer config cache-files-dir)"
+
+      - name: Set up Composer caching
+        uses: actions/cache@v2
+        env:
+          cache-name: cache-composer-dependencies
+        with:
+          path: |
+            ${{ steps.composer-cache.outputs.dir }}
+            /tmp/test-cache
+            /tmp/wordpress
+          key: ${{ runner.os }}-composer-${{ matrix.php }}
+          restore-keys: |
+            ${{ runner.os }}-composer-
+
+      - name: Set up PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: ${{ matrix.php }}
+          extensions: dom, curl, libxml, mbstring, zip, pcntl, pdo, sqlite, pdo_sqlite, gd
+          tools: composer:v2
+          coverage: none
+
+      - name: Install Composer dependencies
+        uses: nick-invision/retry@v2
+        with:
+          timeout_minutes: 5
+          max_attempts: 5
+          command: composer install
+          new_command_on_retry: composer install --ignore-platform-reqs
+
+      - name: Install WordPress and copy project
+        shell: bash
+        run: |
+          bash <(curl -s "https://raw.githubusercontent.com/wp-cli/sample-plugin/master/bin/install-wp-tests.sh") wordpress_test root '' 127.0.0.1 latest
+
+          rm -rf "${WP_CORE_DIR}wp-content/plugins"
+          mkdir -p "${WP_CORE_DIR}wp-content/plugins/wordpress-fieldmanager"
+          rsync -a --exclude=.git . "${WP_CORE_DIR}wp-content/plugins/wordpress-fieldmanager"
+
+      - name: Run tests
+        shell: bash
+        run: |
+          cd ${WP_CORE_DIR}wp-content/plugins/wordpress-fieldmanager
+          composer run phpunit

.gitignore

@@ -1,26 +1,35 @@
-tests/php/build
-tests/php/wp-unit-test
+# Dependencies
+vendor
+node_modules
+.env
+composer.lock
 
-# Silly Macs
-.DS_Store
+# Log files
+*.log
 
-# For those using Git in their SVN
-# ignore files in the WPcom plugin directory
-wpcom-helper.php
-VERSION
-tests/php/tests
-todo.txt
+# Cache files
+.phpcs/*.json
+.phpunit.result.cache
 
-# Created by Apigen for logs
-/build
+# Ignore temporary OS files
+.DS_Store
+.DS_Store?
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+.thumbsdb
 
-/docs
+# IDE files
+*.code-workspace
+.idea
+.vscode
 
-/report/
+# Created by Apigen for logs
+build/
 
-.svn
+# Built docs
+docs/
 
-composer.lock
-/vendor/
-/node_modules
-.idea/
+# Code coverage report
+report/

.phpcs/.gitkeep

@@ -35,22 +35,11 @@ module.exports = function( grunt ) {
 				}
 			}
 		},
-		phpcs: {
-			plugin: {},
-			options: {
-				bin: "vendor/bin/phpcs",
-				showSniffCodes: true,
-				standard: "phpcs.ruleset.xml",
-				verbose: true,
-				warningSeverity: 0,
-			}
-		},
 	});
 
 
 	grunt.loadNpmTasks( 'grunt-contrib-connect' );
 	grunt.loadNpmTasks( 'grunt-contrib-qunit' );
-	grunt.loadNpmTasks( 'grunt-phpcs' );
 
 	grunt.task.run( 'connect' );
 

.travis.yml

@@ -2,28 +2,26 @@
 
 Fieldmanager is a comprehensive toolkit for building forms, metaboxes, and custom admin screens for WordPress.
 
-[![Build Status](https://travis-ci.org/alleyinteractive/wordpress-fieldmanager.svg?branch=master)](https://travis-ci.org/alleyinteractive/wordpress-fieldmanager)
-
 ## Using Fieldmanager in your WordPress Project
 
 Fieldmanager is a powerful library which can make the development of sophisticated features a breeze. To get started, simply [download](#downloads-and-versioning) and install this plugin into your plugins directory and activate it on the plugins screen. To learn how to use Fieldmanager's API, visit the project's official website at [Fieldmanager.org](http://fieldmanager.org). There is also [a demo plugin](https://github.com/alleyinteractive/fieldmanager-demos) which illustrates a lot of what you can do with Fieldmanager.
 
 ## Requirements
 
-* WordPress: 4.7+
-* PHP: 7.0+
+* WordPress: 5.8+
+* PHP: 7.4+
 
-Fieldmanager is tested down to and works on PHP 5.3-5.6, but we don't officially support PHP5. We strongly encourage using PHP7.
+Fieldmanager is tested down to and works on PHP 5.6, but we don't officially support PHP 5. We strongly encourage using PHP 7.4 or 8.
 
 ## Downloads and Versioning.
 
 You can view [Fieldmanager's official releases here](https://github.com/alleyinteractive/wordpress-fieldmanager/releases).
 
-The `master` branch on GitHub is the "bleeding edge" release. As of 1.0, Fieldmanager will maintain a typical release cycle, with alpha, beta, and RC releases, and we hope to move through "minor" versions pretty quickly. While we encourage everyone to develop with and test on early releases and help us find the bugs, stable releases are recommended for production.
+The `main` branch on GitHub is the "bleeding edge" release. As of 1.0, Fieldmanager will maintain a typical release cycle, with alpha, beta, and RC releases, and we hope to move through "minor" versions pretty quickly. While we encourage everyone to develop with and test on early releases and help us find the bugs, stable releases are recommended for production.
 
 ## Contributing to Development
 
-Development of Fieldmanager happens on [Github](http://github.com/alleyinteractive/wordpress-fieldmanager). Bugs with Fieldmanager should be addressed in the Github issue queue, and enhancements or bug fixes should be submitted as pull requests, which are always welcome.
+Development of Fieldmanager happens on [GitHub](http://github.com/alleyinteractive/wordpress-fieldmanager). Bugs with Fieldmanager should be addressed in the GitHub issue queue, and enhancements or bug fixes should be submitted as pull requests, which are always welcome.
 
 ## Generating Documentation