Skip to content
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

List of commands absent on the main git command reference page #1941

Open
j6t opened this issue Jan 22, 2025 · 2 comments · May be fixed by #1942
Open

List of commands absent on the main git command reference page #1941

j6t opened this issue Jan 22, 2025 · 2 comments · May be fixed by #1942

Comments

@j6t
Copy link

j6t commented Jan 22, 2025

The main reference page for the git command, which usually lists all sub-commands, does not list any of these commands.

URL for broken page

https://git-scm.com/docs/git

Problem

The linked page, which shows the manual page of the main git command is titled "Latest version", version 2.48 as of this writing. There is an option to switch to an earlier version. When the version 2.47.0 is selected, the list of commands is present.

In particular, scroll down to High-level commands and further down to Low-level commands. There should be a list of commands with a short summary under each of the sub-sections, but there are none, just the section titles.

I am using Firefox on Linux.

@dscho
Copy link
Member

dscho commented Jan 22, 2025

I suspect this to be a fall-out from git/git@9219325

dscho added a commit to dscho/git-scm.com that referenced this issue Jan 22, 2025
As of Git's 9219325be74 (Documentation: allow sourcing generated
includes from separate dir, 2024-12-06), there are no regular
`include::<path>` statements left that were expected by the
`update-docs.rb` script, but they are now `include::{build_dir}/<path>`
instead.

Let's accommodate for that.

This fixes git#1941

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho linked a pull request Jan 22, 2025 that will close this issue
@dscho dscho linked a pull request Jan 22, 2025 that will close this issue
@dscho
Copy link
Member

dscho commented Jan 22, 2025

Thank you @j6t! Please have a look at #1942.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants