Skip to content

[pull] main from git-for-windows:main #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 630 commits into from
Mar 17, 2025
Merged

Conversation

pull[bot]
Copy link

@pull pull bot commented Mar 17, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

PhilipOakley and others added 30 commits November 6, 2019 11:01
There seems to be a strong preference by the MSYS2 project to have it in
all-capital letters.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Colons are not allowed in Windows filenames...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
…dicting emphasis. This better communicates that the surrounding sentence emphasizes the preceeding, rather than mollifying it
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho and others added 27 commits March 6, 2025 10:32
…h (markdown)"

Contrary to the claim made in this commit, the registry setting is not
required for Git for Windows' long paths support to work.

This reverts commit 6bd107b.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The majority of wiki contributions unfortunately consists of spam,
vandalism, and the occasional misinformation.

To not even let such contributions affect the public (and thereby to
take away one big incentive for such contributions), let's move the wiki
pages to Git for Windows' home page.

This recapitulates what I did with GitGitGadget's wiki (as a blueprint
for doing the same for Git for Windows, not gonna lie).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We are about to migrate all the wiki pages to this site, therefore it
makes sense to have a page listing all of the site's pages.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
These no longer make sense in the Hugo world.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This was accomplished by

  git mv *.png static/img/

and

   git ls-tree --format='%(path)' HEAD^{/^Merge.*wiki}^2 |
   while read path
   do
     test "z$path" != "z${path%.md}" &&
     test -f "$path" ||
     continue

     title="$(echo "${path%.md}" | tr '-' ' ')"

     filename="$(echo "$title" |
       tr 'A-Z' 'a-z' |
       sed 's/[^0-9A-Za-z_]\+/-/g').md"

     sed -i '1i---\ntitle: "'"$title"'"\naliases:\n  - "'"${path%.md}"'"\n---' "$path" &&
     git mv "$path" content/"$filename"
   done

One outlier was `Windows-vs-Linux-fork()/exec()-semantics.md`, which had
to be moved manually.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
You'd need a protocol droid to figure out what protocol to use for
those, and link checkers typically lack such help.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This file name was generated using a simplistic heuristic, but the
result was not quite good, so let's cuddle the "s" with "git".

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The front matter (i.e. the initial part of the `.md` files enclosed
within `---` lines) can be used to specify a title. Let's use that
information in the HTML header to stop calling every single page "Git
for Windows".

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
While all of the headings already have an ID and therefore allow deep
links, it is cumbersome to figure out what the exact ID is.

Let's copy the trick I implemented in
git-for-windows/git-snapshots@3e10e48a and in
git-for-windows/git-snapshots@0dff3b9a: This
will show a clickable link symbol when hovering over a heading.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
It is a no-no to have multiple top-level headers in the same file, see
https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md025.md

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Since the original wiki is no more, it's important to give people a good
explanation why that is, and especially important to avoid giving the
false impression that there is still a Git for Windows wiki.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
While at it, use a sweeter filename.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
There is a "32-bit" page that describes the timeline of Git for Windows'
support for i686 (or more precisely, the timeline of _phasing out_ said
support). There is also a page that describes what problems users run
into when they chose to run the 32-bit version of Git for Windows (now a
bit less relevant because Git for Windows won't produce any new 32-bit
installers). Let's avoid confusion by having two so similarly-named
pages, and instead rename the latter to make it more obvious what it is
all about.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Let's recommend editing Git for Windows' home page instead.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Since we no longer want to let random people edit the wiki, let's not
point readers there, either. The idea is to replace the wiki pages with
links to the corresponding pages on Git for Windows' home page, anyway,
therefore we can point readers there directly.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Thank you, lychee!

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Git for Windows v2.49.0 was the first chance for this new code to be
exercised after switching to a Hugo-generated site. And sure enough,
there were bugs ;-)

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: gitforwindowshelper-bot <gitforwindowshelper-bot@users.noreply.github.com>
In 4b51fcc (Migrate the home page to Hugo (and to Markdown),
2025-03-10), I had migrated also the header that talks about the current
Git for Windows version and where to find it.

Unfortunately, I forgot to update this partial template to take the
variable data from the site parameters, and instead still hard-coded
the version number and similar information.

So let's fix this ;-)

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@pull pull bot added the ⤵️ pull label Mar 17, 2025
@pull pull bot merged commit 3a716f8 into igecloudsdev:main Mar 17, 2025
@pull pull bot had a problem deploying to github-pages March 17, 2025 15:20 Failure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.