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:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user