When a global gh_token is configured, always use it (#1118)

If I configure a global gh_token, I expect it to be used all the time. I expect to see predictable failures when that token is exhausted.
This commit is contained in:
Paul Melnikow
2017-10-29 22:36:39 -04:00
committed by GitHub
parent 090454a828
commit b16122d9a4
2 changed files with 22 additions and 9 deletions

View File

@@ -102,3 +102,11 @@ then you will need to replace `localhost` with the IP address of that virtual
machine.
[shields.example.env]: ../shields.example.env
Server secrets
--------------
You can add your own server secrets in `private/secret.json`. If you specify a
`gh_token` for Github, it will be used in place of the Shields token rotation
logic.