Skip to content

Commit 9b40019

Browse files
committed
community: run 'git bugreport' in your repository
Mention that 'git bugreport' should be run in the repository where the bug was observed, to make sure that any hooks that could be at play are collected and listed in the report. This might lead to less back and forth like in [1]. [1] https://lore.kernel.org/git/CAHBARKezrkKAs0ACbJ_fnxR-qWacQ5KKuVLwn0WyT7aR+4++pQ@mail.gmail.com/T/#u
1 parent 6cf4dd4 commit 9b40019

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

app/views/community/index.html.erb

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,8 @@
5050

5151
<p>
5252
If you are using git 2.27.0 or later, you can run
53-
<a href="/docs/git-bugreport"><span class="fixed">git bugreport</span></a>,
53+
<a href="/docs/git-bugreport"><span class="fixed">git bugreport</span></a> in the repository
54+
where you observed the bug,
5455
which generates a template to guide you through writing a useful bug
5556
report and gathers some diagnostic information about your
5657
environment.

0 commit comments

Comments
 (0)