1GIT-BUGREPORT(1)                  Git Manual                  GIT-BUGREPORT(1)
2
3
4

NAME

6       git-bugreport - Collect information for user to file a bug report
7

SYNOPSIS

9       git bugreport [(-o | --output-directory) <path>] [(-s | --suffix) <format>]
10

DESCRIPTION

12       Captures information about the user’s machine, Git client, and
13       repository state, as well as a form requesting information about the
14       behavior the user observed, into a single text file which the user can
15       then share, for example to the Git mailing list, in order to report an
16       observed bug.
17
18       The following information is requested from the user:
19
20       •   Reproduction steps
21
22       •   Expected behavior
23
24       •   Actual behavior
25
26       The following information is captured automatically:
27
28       •   git version --build-options
29
30       •   uname sysname, release, version, and machine strings
31
32       •   Compiler-specific info string
33
34       •   A list of enabled hooks
35
36       •   $SHELL
37
38       This tool is invoked via the typical Git setup process, which means
39       that in some cases, it might not be able to launch - for example, if a
40       relevant config file is unreadable. In this kind of scenario, it may be
41       helpful to manually gather the kind of information listed above when
42       manually asking for help.
43

OPTIONS

45       -o <path>, --output-directory <path>
46           Place the resulting bug report file in <path> instead of the root
47           of the Git repository.
48
49       -s <format>, --suffix <format>
50           Specify an alternate suffix for the bugreport name, to create a
51           file named git-bugreport-<formatted suffix>. This should take the
52           form of a strftime(3) format string; the current local time will be
53           used.
54

GIT

56       Part of the git(1) suite
57
58
59
60Git 2.31.1                        2021-03-26                  GIT-BUGREPORT(1)
Impressum