Prefer https URLs in documentation #40
Closed
Conversation
This file contains hidden or 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
4aa28e7 to
d764aae
Compare
|
Cancelling this PR - it has excessive reach. Will replace with just the README suggestions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi!
It was suggested to me that I suggest to you to switch the
http:URLs tohttps:in documentation files as a matter of best practice! What do you think?Also, I wonder if you need
ABOUT-NLSat all? It seems a bit dated and probably no use to anyone and I can't see anything to suggest it is required!I think I've checked all the URLs in this PR work. I also updated a couple of addresses to where they currently redirect.