Docs: conditional Travis based on commit message

.travis.yml

@@ -48,6 +48,7 @@ before_script:
 
 stages:
   - name: test
+    if: commit_message !~ /^Docs:/
   - name: release
     if: ((branch = master AND type = push) OR (tag IS present)) AND NOT fork
 
@@ -60,6 +61,8 @@ jobs:
   include:
     # run ci-release only if previous stages passed
     - stage: release
+      name: Publish library
       script: sbt ci-release
     # run website push only if previous stages passed
     - script: sbt docs/docusaurusPublishGhpages
+      name: Publish website

docs/contributing-website.md

@@ -83,3 +83,9 @@ files, build the site and push them to GH pages.
 
 Before running those commands, you might have to change a few constants in
 `siteConfig.js`. These are specifed in the comments of that file.
+
+### CI
+
+Bitcoin-S uses Travis to run tests and deploy library and website builds. Generally
+speaking CI has to pass for a PR to get merged. If you make documentation/website only
+changes, you can start your PR title with `Docs:`. This skips running tests on CI.

docs/contributing.md

@@ -159,3 +159,9 @@ The command `sbt testQuick` can also be handy. It runs tests that either:
 
 For more information on `testQuick`, see the offical
 [sbt docs](https://www.scala-sbt.org/1.x/docs/Testing.html#testQuick).
+
+### CI
+
+Bitcoin-S uses Travis to run tests and deploy library and website builds. Generally
+speaking CI has to pass for a PR to get merged. If you make documentation/website only
+changes, you can start your PR title with `Docs:`. This skips running tests on CI.