Add ProGit v1 redirects #1915

In 2014, the second edition of the ProGit book was started, in 2016 this edition became the default, and in 2020 all v1 URLs were redirected to the landing page of v2. At some stage, the v1 links stopped working, returning a "500 Internal server error". After switching the git-scm.com site to a static Hugo-generated site, those links now return a "404 That page doesn't exist". This is far from an ideal situation. Unfortunately, in a static site, there is no way to install wildcard routes that would redirect to a better URL, therefore we have to enumerate all of the URLs that we want to redirect. Internet Archive to the rescue! This script downloads the tables of contents of the ProGit v1 book and its translations, and determines the URLs that had been active back then, maps them to the v2 equivalents (on a best effort basis), and then writes out a YAML file with that information. Signed-off-by: Johannes Schindelin <[email protected]>

This file was generated by running script/extract-book-v1-urls.rb. Signed-off-by: Johannes Schindelin <[email protected]>

The `File.write(path, content)` form is quite a bit more readable than the long form. Signed-off-by: Johannes Schindelin <[email protected]>

The default language of the ProGit book is English, therefore https://git-scm.com/book should redirect to the table of contents of the English version of that book. This means that the `/external/book/content/book/en/_index.html` file needs to be part of the sparse checkout, otherwise the workflow run would not be able to update it (should it ever become necessary). This was not a problem so far because that file remained unchanged (and is likely to remain so for quite some time yet). Signed-off-by: Johannes Schindelin <[email protected]>

Once upon a time, there first edition of the ProGit book was available on Git's home page, and the sun was shining. Then, one day in 2014, the sun shone brighter and work was begun to write the second edition of this book. At some stage, this became the default when directing web browsers to https://git-scm.com/book, and a few years later, 2020 or so, the links that formerly led to the first edition would redirect to v2. Then, one day, clouds moved across the sky and the redirects from v1 to v2 stopped working and instead a "500 Internal server error" page was shown. Time went by and nobody really knew how to fix it (or more likely, wasn't in the mood, or wanted other people to fix it). Finally, in the fall of 2024, git-scm.com was switched to a static web site, generated using Hugo, and local development became much easier. Naturally, the v1-to-v2 redirects were no longer in place and the v1 links therefore showed 500 no longer, but a 404. Still, nobody knew how to fix it, or wasn't in the mood, or wanted other people to fix it for them. Until now. Now is the day when we resurrect the v1-to-v2 redirects, in even more glory than ever before, for now we redirect to the v2 sections that correspond to the v1 sections (as far as possible, that is)! Only one (slight) fly in the ointment: URLs to v1 sections of the book which contain anchors will keep those anchors as-are, and not translate them to the corresponding new anchors. Example: Git-Basics-Getting-a-Git-Repository#Cloning-an-Existing-Repository should redirect to v2/Git-Basics-Getting-a-Git-Repository#_git_cloning, but does not. It redirects to that page but still tries to find the anchor `#Cloning-an-Existing-Repository`. Alas, this is where I do not know how to fix it, or ain't in the mood, or want other people to fix it for themselves. This commit addresses git#1782 Signed-off-by: Johannes Schindelin <[email protected]>

Updated via the `update-book.yml` GitHub workflow.

…edirects

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add ProGit v1 redirects #1915

Add ProGit v1 redirects #1915

Commits on Nov 11, 2024

Add ProGit v1 redirects #1915

Are you sure you want to change the base?

Add ProGit v1 redirects #1915

Commits on Nov 11, 2024