try to migrate to travis-ci.com. Fixes #447

Author: jacobwilliams

.github/CONTRIBUTING.md

@@ -72,7 +72,7 @@ git rebase upstream/master
 ```
 - Create a branch in your fork with a descriptive name that also includes the [issue number](https://github.com/jacobwilliams/json-fortran/issues), if applicable. For example, after forking the repo, you can run something like `git checkout -b Unicode-support-issue-35` before starting work on [issue #35 : Unicode support](https://github.com/jacobwilliams/json-fortran/issues/35)
 - When you're content with your changes, your commits are clean, self contained, with concise descriptive messages, and your changes compile and pass the tests, submit a pull request. We will review your changes, and may ask for certain modifications to be made.
-- Pull requests are tested by our [travis-ci](https://travis-ci.org/jacobwilliams/json-fortran) continuous integration system, and any errors uncovered will need to be fixed before the pull request can be merged into master.
+- Pull requests are tested by our [travis-ci](https://travis-ci.com/jacobwilliams/json-fortran) continuous integration system, and any errors uncovered will need to be fixed before the pull request can be merged into master.
 - The JSON-Fortran library and associated documentation is released under a BSD style [license](https://github.com/jacobwilliams/json-fortran/blob/master/LICENSE).  By submitting a pull request, you are agreeing to release your code under the same license.  Note that code with GPL or other "copyleft" style licenses will not be accepted.
 
 [top](#contributing-to-json-fortran)

README.md

@@ -21,7 +21,7 @@ A Fortran 2008 JSON API
 
 Status
 ------
-[![Build Status](https://img.shields.io/travis/jacobwilliams/json-fortran/master.svg?style=plastic)](https://travis-ci.org/jacobwilliams/json-fortran)
+[![Build Status](https://img.shields.io/travis/jacobwilliams/json-fortran/master.svg?style=plastic)](https://travis-ci.com/jacobwilliams/json-fortran.svg?branch=master)
 [![GitHub issues](https://img.shields.io/github/issues/jacobwilliams/json-fortran.png?style=plastic)](https://github.com/jacobwilliams/json-fortran/issues)
 [![Codecov](https://codecov.io/gh/jacobwilliams/json-fortran/branch/master/graph/badge.svg)](https://codecov.io/gh/jacobwilliams/json-fortran)
 
@@ -167,7 +167,7 @@ Miscellaneous
 
 * JSON-Fortran is a fork and extensive upgrade of the Fortran 95 [FSON](https://github.com/josephalevin/fson) code. The reason for the split was to be able to incorporate object-oriented and other nice features of the Fortran 2003 and 2008 standards.  Many thanks to the original authors of FSON.
 * For more information about JSON, see: <http://www.json.org/>
-* [json-fortran on Travis CI](https://travis-ci.org/jacobwilliams/json-fortran)
+* [json-fortran on Travis CI](https://travis-ci.com/jacobwilliams/json-fortran)
 * [json-fortran on Codecov.IO](https://codecov.io/gh/jacobwilliams/json-fortran)
 
 [top](#json-fortran)

pages/development-resources/release-checklist.md

@@ -60,7 +60,7 @@ remain accurate.
      1. Note: for some reason, using GitHub to tag a project means that the tag doesn't show up when you `git describe` the project. Tagging from the command line makes `git describe` work as expected.
  1. [deploy.sh](deploy.sh.html) will publish the documentation for the
     latest tag from
-    [Travis-CI](https://travis-ci.org/jacobwilliams/json-fortran) to
+    [Travis-CI](https://travis-ci.com/jacobwilliams/json-fortran) to
     https://jacobwilliams.github.io/json-fortran/*new_ver*/ if all
     goes according to plan
  1. Push tags and master to GitHub: `git push --tags origin master`

pages/development-resources/travis.yml.md

@@ -1,7 +1,7 @@
 title: .travis.yml
 
 This is the
-[Travis-CI](https://travis-ci.org/jacobwilliams/json-fortran) script
+[Travis-CI](https://travis-ci.com/jacobwilliams/json-fortran) script
 used to perform continuous integration testing for JSON-Fortran, and
 trigger automatic documentation deployment.