Add "strictTls" setting option #23
Merged
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
Closed
|
Hi @grzegorzjudas , First of all, thanks for you PR, and sorry for taking so long to comment here. I will take a look this weekend, and publish an update. Stay tuned 👍 |
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.
Add a "strictTls" option
Provides support for strictTls property to settings that you can set to false if you have TLS certificates problems.
Defaults to true and should not be changing it is not recommended, but may be required if you've got certificate problems with Github (for example, Enterprise Githubs, hosted internally).
Note:
Also includes package.json format fixes (my IDE fixed it by itself).