travis 1.8.14.travis.1192.9 → 1.8.14.travis.1195.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c29e2c7afadd73bcd41f54f47e42b98c5bb8f3babf59e2a8329613e591d9718a
-  data.tar.gz: 740578751cc88b55e9ce3946b7c4cfb1a7fa825f7901bd747a6a76f631ee7e1e
+  metadata.gz: 771452c7b510fbfae503ade3f4ec52605b453cc7818aab23113db62ac9d89b1b
+  data.tar.gz: 34e50020d48749958a1b216832d860572c961db49c61bc568c46cd241d238237
 SHA512:
-  metadata.gz: 3c8c1b6bcfff3dadab84c0aefeba5a1956ef6d0285dac4975ea9d2aa6b0a566a25fca3e91bb2bc36cc443d9c8953e3a0844377918d5fff0e36889e8fd52d98b0
-  data.tar.gz: 67ceae7bfa3d8ed6b0c7b159c2b55ea1ae02d5cdc2b141d6d08bd6a058e292fffc0f9bf5c123cfe82805417611477ec3f1ea19e2cffeba53000531903164874f
+  metadata.gz: 9c4fff3659c7dd5c942a2caef77ffdc7148337c4e9e54b73578891ae63baab1214258a515824904651c1067b0a9e94215a06d07265cc4866abb356f451f3de11
+  data.tar.gz: 62a2a0e6b897729e2ebe5d205f2afd8fbfbf99aaaeadfda283479afb14464211fbc2bdc1465e7dab052dfdf3dc706786340de3943e1ebb427a826e5380eea124

data/README.md

@@ -249,6 +249,7 @@ Successfully logged in!
 As you can see above, it will ask you for your GitHub user name and password, but not send these to Travis CI. Instead, it will use them to create a GitHub API token, show the token to Travis, which then on its own checks if you really are who you say you are, and gives you an access token for the Travis API in return. The client will then delete the GitHub token again, just to be sure. But don't worry, all that happens under the hood and fully automatic.
 
 If you don't want it to send your credentials to GitHub, you can create a GitHub token on your own and supply it via `--github-token`. In that case, the client will not delete the GitHub token (as it can't, it needs your password to do this). Travis CI will not store the token, though - after all, it already should have a valid token for you in the database.
+*NOTE*: When creating a GitHub token, see [GitHub Permissions used by travis-ci.com](https://docs.travis-ci.com/user/github-oauth-scopes/#travis-ci-for-private-projects) or [GitHub Permissions used by travis-ci.org](https://docs.travis-ci.com/user/github-oauth-scopes/#travis-ci-for-open-source-projects). The token permissions are dependent on use of travis-ci.com or travis-ci.org and not if they are public or private repositories.
 
 A third option is for the really lazy: `--auto`. In this mode the client will try to find a GitHub token for you and just use that. This will only work if you have a [global GitHub token](https://help.github.com/articles/git-over-https-using-oauth-token) stored in your [.netrc](http://blogdown.io/c4d42f87-80dd-45d5-8927-4299cbdf261c/posts/574baa68-f663-4dcf-88b9-9d41310baf2f). If you haven't heard of this, it's worth looking into in general. Again: Travis CI will not store that token.
 

data/travis.gemspec

@@ -74,7 +74,8 @@ Gem::Specification.new do |s|
     "Titus",
     "Titus Wormer",
     "designerror",
-    "ia"
+    "ia",
+    "slewt"
   ]
 
   # generated from git shortlog -sne
@@ -144,7 +145,8 @@ Gem::Specification.new do |s|
     "tituswormer@gmail.com",
     "carla@travis-ci.org",
     "designerror@yandex.ru",
-    "isaac.ardis@gmail.com"
+    "isaac.ardis@gmail.com",
+    "leland@lcweathers.net"
   ]
 
   # generated from git ls-files

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: travis
 version: !ruby/object:Gem::Version
-  version: 1.8.14.travis.1192.9
+  version: 1.8.14.travis.1195.9
 platform: ruby
 authors:
 - Hiro Asari
@@ -67,10 +67,11 @@ authors:
 - Titus Wormer
 - designerror
 - ia
+- slewt
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-04-14 00:00:00.000000000 Z
+date: 2020-04-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday
@@ -314,6 +315,7 @@ email:
 - carla@travis-ci.org
 - designerror@yandex.ru
 - isaac.ardis@gmail.com
+- leland@lcweathers.net
 executables:
 - travis
 extensions: []