changed OAuth token for doc deployment from Travis CI #1338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- fixes #1337 - new token was generated because the old token was exposed due to a security incident at Travis CI, see https://blog.travis-ci.com/2017-05-08-security-advisory - followed #386 for generating new token and encrypting for Travis CI
kain88-de
approved these changes
May 9, 2017
|
FYI: I added a wiki page on OAuth tokens for doc deployment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1337
Changes made in this Pull Request:
incident at Travis CI, see https://blog.travis-ci.com/2017-05-08-security-advisory
PR Checklist