Just give GHA a little bit priority over Travis

As far as we are removing Travis CI from core (see MDLSITE-7135)
this just applies small tweaks to all the places where stuff related
with Travis is documented, always trying to put the GHA alternative
earlier in the doc.

Basically moving a few paragraphs around and some little details
here and there.

Author: stronk7

docs/AddExtraConfig.md

@@ -5,10 +5,9 @@ title: Adding extra configs to Moodle's configuration file
 
 Sometimes a plugin may require extra config in the Moodle `config.php` file because, for example, it interacts with a
 non-standard service.  This project provides a way to update the `config.php` file with the `add-config` command.  Here
-is an example of how to use it in your `.travis.yml` file:
+is an example of how to use it in your `.github/workflow/*` or `.travis.yml` files:
 
 ```yaml
-install:
   - moodle-plugin-ci install
   - moodle-plugin-ci add-config '$CFG->foo = "bar";'
   - moodle-plugin-ci add-config 'define("BAT", "baz");'
@@ -19,6 +18,7 @@ The first `add-config` call will add `$CFG->foo = "bar";` to the config file and
 `define("BAT", "baz");` to the config file, after our first line.
 
 Some things to keep in mind when crafting these calls to `add-config`:
+
 * You might be tempted to reverse the quotes because normally single quotes are used for strings in PHP.  While this is
   true, we are also using Bash here and using double quotes will cause several problems.  In particular, Bash will try
   to evaluate the string and replace things like `$CFG` with a Bash variable.

docs/AddExtraPlugins.md

@@ -5,10 +5,9 @@ title: Adding extra plugins
 
 Sometimes the plugin that you are testing may depend on another plugin or even several other plugins.  This project
 provides a way to Git clone the extra plugins and add them to the Moodle test site. Here is an example of how to use
-it in your `.travis.yml` file:
+it in your `.github/workflow/*` or `.travis.yml` files:
 
 ```yaml
-install:
   - moodle-plugin-ci add-plugin moodlehq/moodle-local_hub
   - moodle-plugin-ci install
 ```

docs/CHANGELOG.md

@@ -9,6 +9,8 @@ This project adheres to [Semantic Versioning](http://semver.org/).
 The format of this change log follows the advice given at [Keep a CHANGELOG](http://keepachangelog.com).
 
 ## [Unreleased]
+### Changed
+- Small changes to documentation towards prioritise GitHub Actions over Travis CI.
 
 ## [3.4.11] - 2023-03-22
 ### Changed

docs/Help.md

@@ -5,13 +5,12 @@ title: Help
 
 ## Change log
 
-Always a good idea to check the [change log](CHANGELOG.md) if something suddenly breaks or behavior
-changed.  Also a good place to look for new goodies.
+Always a good idea to check the [change log](CHANGELOG.md) if something suddenly breaks or behaviour changed.  Also a good place to look for new goodies.
 
 ## Help topics
 
-* [Travis CI file explained](TravisFileExplained.md): every line of the `.travis.dist.yml` file explained.
 * [GitHub Actions workflow file explained](GHAFileExplained.md): every line of the `gha.dist.yml` file explained.
+* [Travis CI file explained](TravisFileExplained.md): every line of the `.travis.dist.yml` file explained.
 * [Add extra Moodle configs](AddExtraConfig.md): how to add extra configs to Moodle `config.php`.
 * [Add extra plugins](AddExtraPlugins.md): how to add plugin dependencies to Moodle.
 * [Ignoring files](IgnoringFiles.md): how to ignore files that might be causing failures.

docs/IgnoringFiles.md

@@ -14,19 +14,6 @@ using specific PHP comments.  For details see this
 In addition, you can ignore additional files by defining `IGNORE_PATHS` and/or `IGNORE_NAMES` environment variables
 in your CI workflow file.  These environment variables wont work for Grunt tasks, but will for everything else.
 
-`.travis.yml` example:
-
-```yaml
-env:
- global:
-  - MOODLE_BRANCH=MOODLE_32_STABLE
-  - IGNORE_PATHS=vendor/widget,javascript/min-lib.js
-  - IGNORE_NAMES=*-m.js,bad_lib.php
- matrix:
-  - DB=pgsql
-  - DB=mysqli
-```
-
 `.github/workflow/*` example:
 
 ```yaml
@@ -40,28 +27,27 @@ env:
           IGNORE_NAMES: '*-m.js,bad_lib.php'
 ```
 
-Both environment variables take a CSV value.  For `IGNORE_PATHS`, it takes relative file paths to ignore.  File paths
-can be a simple string like `foo/bar` or a regular expression like `/^foo\/bar/`.  For `IGNORE_NAMES`, it takes
-file names to ignore.  File names can be a simple string like `foo.php`, a glob like `*.php` or a regular expression
-like `/\.php$/`.
-
-If you need to specify ignore paths for a specific command, then you can define additional environment variables.  The
-variable names are the same as above, but prefixed with `COMMANDNAME_`.
-
 `.travis.yml` example:
 
 ```yaml
 env:
  global:
   - MOODLE_BRANCH=MOODLE_32_STABLE
-  - CODECHECKER_IGNORE_PATHS=vendor/widget,javascript/min-lib.js
-  - CODECHECKER_IGNORE_NAMES=*-m.js,bad_lib.php
-  - PHPUNIT_IGNORE_PATHS=$IGNORE_PATHS,cli
+  - IGNORE_PATHS=vendor/widget,javascript/min-lib.js
+  - IGNORE_NAMES=*-m.js,bad_lib.php
  matrix:
   - DB=pgsql
   - DB=mysqli
 ```
 
+Both environment variables take a CSV value.  For `IGNORE_PATHS`, it takes relative file paths to ignore.  File paths
+can be a simple string like `foo/bar` or a regular expression like `/^foo\/bar/`.  For `IGNORE_NAMES`, it takes
+file names to ignore.  File names can be a simple string like `foo.php`, a glob like `*.php` or a regular expression
+like `/\.php$/`.
+
+If you need to specify ignore paths for a specific command, then you can define additional environment variables.  The
+variable names are the same as above, but prefixed with `COMMANDNAME_`.
+
 `.github/workflow/*` example:
 
 ```yaml
@@ -76,6 +62,20 @@ env:
           MUSTACHE_IGNORE_NAMES: 'broken.mustache'
 ```
 
+`.travis.yml` example:
+
+```yaml
+env:
+ global:
+  - MOODLE_BRANCH=MOODLE_32_STABLE
+  - CODECHECKER_IGNORE_PATHS=vendor/widget,javascript/min-lib.js
+  - CODECHECKER_IGNORE_NAMES=*-m.js,bad_lib.php
+  - PHPUNIT_IGNORE_PATHS=$IGNORE_PATHS,cli
+ matrix:
+  - DB=pgsql
+  - DB=mysqli
+```
+
 In the above example, we are adding the `cli` path to our ignore paths for the PHPUnit command (this is also how you
 can ignore files for code coverage).  Please note that this is a complete override and there is no merging with
 `IGNORE_PATHS` and `IGNORE_NAMES`.  So, in the above, the PHPUnit command would not ignore the file names

docs/ReleaseNewVersion.md

@@ -13,9 +13,9 @@ Prior to tagging a release, ensure the following have been updated:
 * The `bin/moodle-plugin-ci` also needs to be updated accordingly, setting the `MOODLE_PLUGIN_CI_VERSION` constant
   to the version being released.
 * If this is a new major version, then CI tool example files and its docs need
-  to be updated to use the new major version (e.g. for Travis CI make changes
-  in `.travis.dist.yml` and `doc/TravisFileExplained.md`). Any other version
-  will automatically be used.
+  to be updated to use the new major version (e.g. for GitHub Actions
+  CI make changes in `gha.dist.yml` and `docs/GHAFileExplained.md`).
+  Any other version will automatically be used.
 
 When all the changes above have been performed, push them straight upstream to
 `master` or create a standard PR to get them reviewed and incorporated

docs/index.md

@@ -8,9 +8,9 @@ analysis against a Moodle plugin in CI tool of your choice. All of these tests
 and tools are run everytime a change is pushed to a GitHub branch or pull
 request.
 
-We currently provide user manual how to use it with [Travis
-CI](https://travis-ci.com) and [GitHub
-Actions](https://docs.github.com/en/actions), if you are using
+We currently provide user manual how to use it with [GitHub
+Actions](https://docs.github.com/en/actions) and [Travis
+CI](https://travis-ci.com), if you are using
 `moodle-plugin-ci` with other CI services please do share your setup examples
 by creating a ticket.
 
@@ -20,6 +20,7 @@ because you can be more confident that the change wont break anything.  There ar
 tools, like being able to test your code against multiple databases, multiple PHP versions, etc.
 
 This project supports the following testing frameworks and code analysis tools:
+
 * [PHPUnit](https://phpunit.de)
 * [Behat](http://behat.org/)
 * [Moodle Code Checker](https://github.com/moodlehq/moodle-local_codechecker)
@@ -46,23 +47,6 @@ Please know older versions (1 and 2) are no longer getting new features and may
 
 Follow steps to get your Moodle plugin building in CI tool of your choice.
 
-### Travis CI
-
-#### Step 1
-
-Sign into [Travis CI](https://travis-ci.com) with your GitHub account. Once you’re signed in, and Travis CI will have
-synchronized your repositories from GitHub.  Go to your [profile](https://travis-ci.com/profile) page and enable Travis CI
-for the plugin you want to build.  Now whenever your plugin receives an update or gets a new pull request, Travis CI will
-run a build to make sure nothing broke.
-
-#### Step 2
-
-Copy the [.travis.dist.yml](https://github.com/moodlehq/moodle-plugin-ci/blob/master/.travis.dist.yml) file into the
-root of your plugin and rename it to `.travis.yml`. Now might be a good time to review the `.travis.yml` contents and
-remove anything that is not needed.  See this [help document](TravisFileExplained.md) for an explanation about the
-contents of the this file. Once you have added the `.travis.yml` file, commit and push up to GitHub, to trigger a
-Travis CI build. Navigate back to [Travis CI](https://travis-ci.com) to see if your build passes or fails.
-
 ### GitHub Actions
 
 #### Step 1
@@ -81,6 +65,23 @@ Start manual](https://docs.github.com/en/actions/quickstart#viewing-your-workflo
 useful. Now whenever you push commits to your plugin repo or it gets a new
 pull request, GitHub will run a build to make sure nothing broke.
 
+### Travis CI
+
+#### Step 1
+
+Sign into [Travis CI](https://travis-ci.com) with your GitHub account. Once you’re signed in, and Travis CI will have
+synchronized your repositories from GitHub.  Go to your [profile](https://travis-ci.com/profile) page and enable Travis CI
+for the plugin you want to build.  Now whenever your plugin receives an update or gets a new pull request, Travis CI will
+run a build to make sure nothing broke.
+
+#### Step 2
+
+Copy the [.travis.dist.yml](https://github.com/moodlehq/moodle-plugin-ci/blob/master/.travis.dist.yml) file into the
+root of your plugin and rename it to `.travis.yml`. Now might be a good time to review the `.travis.yml` contents and
+remove anything that is not needed.  See this [help document](TravisFileExplained.md) for an explanation about the
+contents of the this file. Once you have added the `.travis.yml` file, commit and push up to GitHub, to trigger a
+Travis CI build. Navigate back to [Travis CI](https://travis-ci.com) to see if your build passes or fails.
+
 ### Getting more of CI
 
 Next steps on your continuous build journey may include: