2 .\" Title: git-bugreport
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
7 .\" Source: Git 2.44.0.rc2
10 .TH "GIT\-BUGREPORT" "1" "2024\-02\-19" "Git 2\&.44\&.0\&.rc2" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-bugreport \- Collect information for user to file a bug report
35 \fIgit bugreport\fR [(\-o | \-\-output\-directory) <path>] [(\-s | \-\-suffix) <format>]
36 [\-\-diagnose[=<mode>]]
41 Collects information about the user\(cqs machine, Git client, and repository state, in addition to a form requesting information about the behavior the user observed, and stores it in a single text file which the user can then share, for example to the Git mailing list, in order to report an observed bug\&.
43 The following information is requested from the user:
78 The following information is captured automatically:
88 \fIgit version \-\-build\-options\fR
99 uname sysname, release, version, and machine strings
110 Compiler\-specific info string
121 A list of enabled hooks
135 Additional information may be gathered into a separate zip archive using the \fB\-\-diagnose\fR option, and can be attached alongside the bugreport document to provide additional context to readers\&.
137 This tool is invoked via the typical Git setup process, which means that in some cases, it might not be able to launch \- for example, if a relevant config file is unreadable\&. In this kind of scenario, it may be helpful to manually gather the kind of information listed above when manually asking for help\&.
140 \-o <path>, \-\-output\-directory <path>
142 Place the resulting bug report file in
144 instead of the current directory\&.
147 \-s <format>, \-\-suffix <format>
149 Specify an alternate suffix for the bugreport name, to create a file named
150 \fIgit\-bugreport\-<formatted\-suffix>\fR\&. This should take the form of a strftime(3) format string; the current local time will be used\&.
153 \-\-no\-diagnose, \-\-diagnose[=<mode>]
155 Create a zip archive of supplemental information about the user\(cqs machine, Git client, and repository state\&. The archive is written to the same output directory as the bug report and is named
156 \fIgit\-diagnostics\-<formatted\-suffix>\fR\&.
160 specified, the diagnostic archive will contain the default set of statistics reported by
161 \fBgit diagnose\fR\&. An optional
163 value may be specified to change which information is included in the archive\&. See
164 \fBgit-diagnose\fR(1)
165 for the list of valid values for
167 and details about their usage\&.
171 Part of the \fBgit\fR(1) suite