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.
Changes
Context
#1953 tried to ensure that no links to
http://git-scm.com/
were part of the deployment (note the missing "s" in "http").Unfortunately, there are plenty of such links to go around, most of them in translations of the ProGit book (out of our control) and the remaining ones in the
gitweb.conf
manual pages related to Git versions prior to v2.13.0 (specifically, before commit git/git@e52a53d).This caused the
deploy
workflow run to fail.I've added a work-around in this here PR by manually forcing
http://
-only links specifically to git-scm.com in thebook/
anddocs/
pages tohttps://
ones.To make sure that this kind of problem is caught in PRs before merging, I've also extended the check to catch
http://git-scm.com
links also when deploying to a fork. To verify that this works as intended, I deployed to my fork with these changes, which was successful, and then I deployed with the fix reverted (for testing), which failed as expected./cc @b9a1