browserify link: HTTP => HTTPS #14721
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
|
|
|
For maintainers only:
|
vankop
approved these changes
Nov 13, 2021
|
@Schweinepriester The most important CI builds failed. This way your PR can't be merged. Please take a look at the CI results from azure (1 errors / 6 warnings) and appveyor (success) and fix these issues. |
snitin315
approved these changes
Nov 13, 2021
|
Thanks |
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.
What kind of change does this PR introduce?
Doc change only.
Checked the link, skipping the redirect HTTP => HTTPS this way 0:-)
There are 3 more HTTP-only links, but they sadly have to remain as is, since HTTPS is not available for them.
Did you add tests for your changes?
Not applicable.
Does this PR introduce a breaking change?
No.
What needs to be documented once your changes are merged?
Nothing.