[PATCH] bugreport: add quoted line prefixes

[PATCH] bugreport: add quoted line prefixes

[Felipe Contreras]

With quoted line prefixes it's easier to distinguish what are the
standard questions, and what are the user responses.

Additionally it's easier for the reporter to visualize what has she
responded.

Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---

Lately I've seen a bunch of bug reports on the mailing list, but I find
it hard to parse the questions from the responses.

 builtin/bugreport.c | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/builtin/bugreport.c b/builtin/bugreport.c
index 9915a5841d..10e55afe37 100644
--- a/builtin/bugreport.c
+++ b/builtin/bugreport.c
@@ -94,21 +94,21 @@ static const char * const bugreport_usage[] = {
 static int get_bug_template(struct strbuf *template)
 {
 	const char template_text[] = N_(
-"Thank you for filling out a Git bug report!\n"
-"Please answer the following questions to help us understand your issue.\n"
+"> Thank you for filling out a Git bug report!\n"
+"> Please answer the following questions to help us understand your issue.\n"
 "\n"
-"What did you do before the bug happened? (Steps to reproduce your issue)\n"
+"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
 "\n"
-"What did you expect to happen? (Expected behavior)\n"
+"> What did you expect to happen? (Expected behavior)\n"
 "\n"
-"What happened instead? (Actual behavior)\n"
+"> What happened instead? (Actual behavior)\n"
 "\n"
-"What's different between what you expected and what actually happened?\n"
+"> What's different between what you expected and what actually happened?\n"
 "\n"
-"Anything else you want to add:\n"
+"> Anything else you want to add:\n"
 "\n"
-"Please review the rest of the bug report below.\n"
-"You can delete any lines you don't wish to share.\n");
+"> Please review the rest of the bug report below.\n"
+"> You can delete any lines you don't wish to share.\n");
 
 	strbuf_addstr(template, _(template_text));
 	return 0;
-- 
2.32.0.40.gb9b36f9b52

[PATCH v2] bugreport: use quoted line prefixes

[kristofferhaugsbakk]

From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Quoted line prefixes make it easier to distinguish between the questions
and the answers, both for the reporter and for the readers.

Based-on-patch-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---

Notes (series):
    § Changes in v2
    
    • Update test which wasn’t there when v1 was made
    • Rewrite commit message to one single sentence
    • “use” in the subject is slightly more declarative than “add” (?)

 builtin/bugreport.c  | 18 +++++++++---------
 t/t0091-bugreport.sh | 18 +++++++++---------
 2 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/builtin/bugreport.c b/builtin/bugreport.c
index f78c3f2aed6..44be7eb4859 100644
--- a/builtin/bugreport.c
+++ b/builtin/bugreport.c
@@ -65,21 +65,21 @@ static const char * const bugreport_usage[] = {
 static int get_bug_template(struct strbuf *template)
 {
 	const char template_text[] = N_(
-"Thank you for filling out a Git bug report!\n"
-"Please answer the following questions to help us understand your issue.\n"
+"> Thank you for filling out a Git bug report!\n"
+"> Please answer the following questions to help us understand your issue.\n"
 "\n"
-"What did you do before the bug happened? (Steps to reproduce your issue)\n"
+"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
 "\n"
-"What did you expect to happen? (Expected behavior)\n"
+"> What did you expect to happen? (Expected behavior)\n"
 "\n"
-"What happened instead? (Actual behavior)\n"
+"> What happened instead? (Actual behavior)\n"
 "\n"
-"What's different between what you expected and what actually happened?\n"
+"> What's different between what you expected and what actually happened?\n"
 "\n"
-"Anything else you want to add:\n"
+"> Anything else you want to add:\n"
 "\n"
-"Please review the rest of the bug report below.\n"
-"You can delete any lines you don't wish to share.\n");
+"> Please review the rest of the bug report below.\n"
+"> You can delete any lines you don't wish to share.\n");
 
 	strbuf_addstr(template, _(template_text));
 	return 0;
diff --git a/t/t0091-bugreport.sh b/t/t0091-bugreport.sh
index e38ca7a9018..9d7008f3592 100755
--- a/t/t0091-bugreport.sh
+++ b/t/t0091-bugreport.sh
@@ -12,21 +12,21 @@ test_expect_success 'create a report' '
 test_expect_success 'report contains wanted template (before first section)' '
 	sed -ne "/^\[/q;p" git-bugreport-format.txt >actual &&
 	cat >expect <<-\EOF &&
-	Thank you for filling out a Git bug report!
-	Please answer the following questions to help us understand your issue.
+	> Thank you for filling out a Git bug report!
+	> Please answer the following questions to help us understand your issue.
 
-	What did you do before the bug happened? (Steps to reproduce your issue)
+	> What did you do before the bug happened? (Steps to reproduce your issue)
 
-	What did you expect to happen? (Expected behavior)
+	> What did you expect to happen? (Expected behavior)
 
-	What happened instead? (Actual behavior)
+	> What happened instead? (Actual behavior)
 
-	What'\''s different between what you expected and what actually happened?
+	> What'\''s different between what you expected and what actually happened?
 
-	Anything else you want to add:
+	> Anything else you want to add:
 
-	Please review the rest of the bug report below.
-	You can delete any lines you don'\''t wish to share.
+	> Please review the rest of the bug report below.
+	> You can delete any lines you don'\''t wish to share.
 
 
 	EOF

Range-diff against v1:
1:  ef7a1cbd9d4 ! 1:  52a6177e706 bugreport: add quoted line prefixes
    @@
      ## Metadata ##
    -Author: Felipe Contreras <felipe.contreras@gmail.com>
    +Author: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
      ## Commit message ##
    -    bugreport: add quoted line prefixes
    +    bugreport: use quoted line prefixes
     
    -    With quoted line prefixes it's easier to distinguish what are the
    -    standard questions, and what are the user responses.
    +    Quoted line prefixes make it easier to distinguish between the questions
    +    and the answers, both for the reporter and for the readers.
     
    -    Additionally it's easier for the reporter to visualize what has she
    -    responded.
    +    Based-on-patch-by: Felipe Contreras <felipe.contreras@gmail.com>
    +    Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
    -    Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
    +
    + ## Notes (series) ##
    +    § Changes in v2
    +
    +    • Update test which wasn’t there when v1 was made
    +    • Rewrite commit message to one single sentence
    +    • “use” in the subject is slightly more declarative than “add” (?)
     
      ## builtin/bugreport.c ##
     @@ builtin/bugreport.c: static const char * const bugreport_usage[] = {
    @@ builtin/bugreport.c: static const char * const bugreport_usage[] = {
      
      	strbuf_addstr(template, _(template_text));
      	return 0;
    +
    + ## t/t0091-bugreport.sh ##
    +@@ t/t0091-bugreport.sh: test_expect_success 'create a report' '
    + test_expect_success 'report contains wanted template (before first section)' '
    + 	sed -ne "/^\[/q;p" git-bugreport-format.txt >actual &&
    + 	cat >expect <<-\EOF &&
    +-	Thank you for filling out a Git bug report!
    +-	Please answer the following questions to help us understand your issue.
    ++	> Thank you for filling out a Git bug report!
    ++	> Please answer the following questions to help us understand your issue.
    + 
    +-	What did you do before the bug happened? (Steps to reproduce your issue)
    ++	> What did you do before the bug happened? (Steps to reproduce your issue)
    + 
    +-	What did you expect to happen? (Expected behavior)
    ++	> What did you expect to happen? (Expected behavior)
    + 
    +-	What happened instead? (Actual behavior)
    ++	> What happened instead? (Actual behavior)
    + 
    +-	What'\''s different between what you expected and what actually happened?
    ++	> What'\''s different between what you expected and what actually happened?
    + 
    +-	Anything else you want to add:
    ++	> Anything else you want to add:
    + 
    +-	Please review the rest of the bug report below.
    +-	You can delete any lines you don'\''t wish to share.
    ++	> Please review the rest of the bug report below.
    ++	> You can delete any lines you don'\''t wish to share.
    + 
    + 
    + 	EOF

base-commit: 724518f3884d8707c5f51428ba98c115818229b8
-- 
2.50.1

Re: [PATCH v2] bugreport: use quoted line prefixes

[Junio C Hamano]

kristofferhaugsbakk@fastmail.com writes:

> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> Quoted line prefixes make it easier to distinguish between the questions
> and the answers, both for the reporter and for the readers.

This may improve things a bit, but the #1 thing that made the
reports most hard to read for me, while reading bugreport output
posted here over time, is lack of a blank line between each question
and its answer (and the tail end of an answer and the beginning of
the next question).

I wonder if there are things we can do to encourage reporters to
leave blank lines around what they write?

> -"Thank you for filling out a Git bug report!\n"
> -"Please answer the following questions to help us understand your issue.\n"
> +"> Thank you for filling out a Git bug report!\n"
> +"> Please answer the following questions to help us understand your issue.\n"
>  "\n"

I do not see a need to quote the above.  Nobody will write in this
space between the above introductory text and the first question
below.

> -"What did you do before the bug happened? (Steps to reproduce your issue)\n"
> +"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
>  "\n"

Here is one blank line between this question and the next question.
If the reporter typed on that blank line, we end up with an
uninterrupted sequence of questions and answers.

I wonder if it helps if we did:

 - Give more blank lines upfront, like three lines, making it

	> We ask you a question here...



	> We ask you another question here...

 - Give a stronger prompt to guide them where to write their answer.

	Q1. We ask you a question here...

	A1.

	Q2. We ask you another question here...

I suspec that the latter might result in what we want, without
annoying the repoter too much.  We could also do

	> We ask you a question here ...

        (please write your answer here)

	> We ask you another question here ...

but that would make them remove that place-holding prompt, which
would be annoying, and at the same time, tempt them to remove the
blank lines around it.  The fewer things we make them remove, the
better chance we have to achieve what we want, I think.

Thanks.

[PATCH v3] bugreport: use quoted line prefixes & more blank lines

[kristofferhaugsbakk]

From: Kristoffer Haugsbakk <code@khaugsbakk.name>

Quoted line prefixes make it easier to distinguish between the questions
and the answers, both for the reporter and for the readers.

Also try to nudge the user to submit a report with a blank line
separating the end of the question, the answer, and the next
question.[1]  (Or leave optional answers empty, i.e. with three
blank lines.  That should be fine too.)

[1]: Suggested by Junio

Based-on-patch-by: Felipe Contreras <felipe.contreras@gmail.com>
Suggested-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---

Notes (series):
    § Changes in v3
    
    • Don’t quote the introduction (not a question and not needed)
    • Also try to nudge the user to leave enough blank lines
    • Keep using one single patch for less test file churn even though these
      are two changes in one
    
    I considered being cute with the footnote:
    
        ...
        question.[1] ...
    
        Based-on-patch-by: Felipe Contreras <felipe.contreras@gmail.com>
        [1]:
        Suggested-by: Junio C Hamano <gitster@pobox.com>
        Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
    
    § Changes in v2
    
    • Update test which wasn’t there when v1 was made
    • Rewrite commit message to one single sentence
    • “use” in the subject is slightly more declarative than “add” (?)

 builtin/bugreport.c  | 27 ++++++++++++++++++++-------
 t/t0091-bugreport.sh | 27 ++++++++++++++++++++-------
 2 files changed, 40 insertions(+), 14 deletions(-)

diff --git a/builtin/bugreport.c b/builtin/bugreport.c
index f78c3f2aed6..694ab85d8cb 100644
--- a/builtin/bugreport.c
+++ b/builtin/bugreport.c
@@ -67,19 +67,32 @@ static int get_bug_template(struct strbuf *template)
 	const char template_text[] = N_(
 "Thank you for filling out a Git bug report!\n"
 "Please answer the following questions to help us understand your issue.\n"
+"There are three blank lines after each question; please write your\n"
+"response on the second line and keep a blank line betweeen the question\n"
+"and the answer (beginning and end).\n"
 "\n"
-"What did you do before the bug happened? (Steps to reproduce your issue)\n"
+"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
 "\n"
-"What did you expect to happen? (Expected behavior)\n"
 "\n"
-"What happened instead? (Actual behavior)\n"
 "\n"
-"What's different between what you expected and what actually happened?\n"
+"> What did you expect to happen? (Expected behavior)\n"
 "\n"
-"Anything else you want to add:\n"
 "\n"
-"Please review the rest of the bug report below.\n"
-"You can delete any lines you don't wish to share.\n");
+"\n"
+"> What happened instead? (Actual behavior)\n"
+"\n"
+"\n"
+"\n"
+"> What's different between what you expected and what actually happened?\n"
+"\n"
+"\n"
+"\n"
+"> Anything else you want to add:\n"
+"\n"
+"\n"
+"\n"
+"> Please review the rest of the bug report below.\n"
+"> You can delete any lines you don't wish to share.\n");
 
 	strbuf_addstr(template, _(template_text));
 	return 0;
diff --git a/t/t0091-bugreport.sh b/t/t0091-bugreport.sh
index e38ca7a9018..facaf1a5373 100755
--- a/t/t0091-bugreport.sh
+++ b/t/t0091-bugreport.sh
@@ -14,19 +14,32 @@ test_expect_success 'report contains wanted template (before first section)' '
 	cat >expect <<-\EOF &&
 	Thank you for filling out a Git bug report!
 	Please answer the following questions to help us understand your issue.
+	There are three blank lines after each question; please write your
+	response on the second line and keep a blank line betweeen the question
+	and the answer (beginning and end).
 
-	What did you do before the bug happened? (Steps to reproduce your issue)
+	> What did you do before the bug happened? (Steps to reproduce your issue)
 
-	What did you expect to happen? (Expected behavior)
 
-	What happened instead? (Actual behavior)
 
-	What'\''s different between what you expected and what actually happened?
+	> What did you expect to happen? (Expected behavior)
 
-	Anything else you want to add:
 
-	Please review the rest of the bug report below.
-	You can delete any lines you don'\''t wish to share.
+
+	> What happened instead? (Actual behavior)
+
+
+
+	> What'\''s different between what you expected and what actually happened?
+
+
+
+	> Anything else you want to add:
+
+
+
+	> Please review the rest of the bug report below.
+	> You can delete any lines you don'\''t wish to share.
 
 
 	EOF

Interdiff against v2:
  diff --git a/builtin/bugreport.c b/builtin/bugreport.c
  index 44be7eb4859..694ab85d8cb 100644
  --- a/builtin/bugreport.c
  +++ b/builtin/bugreport.c
  @@ -65,19 +65,32 @@ static const char * const bugreport_usage[] = {
   static int get_bug_template(struct strbuf *template)
   {
   	const char template_text[] = N_(
  -"> Thank you for filling out a Git bug report!\n"
  -"> Please answer the following questions to help us understand your issue.\n"
  +"Thank you for filling out a Git bug report!\n"
  +"Please answer the following questions to help us understand your issue.\n"
  +"There are three blank lines after each question; please write your\n"
  +"response on the second line and keep a blank line betweeen the question\n"
  +"and the answer (beginning and end).\n"
   "\n"
   "> What did you do before the bug happened? (Steps to reproduce your issue)\n"
   "\n"
  +"\n"
  +"\n"
   "> What did you expect to happen? (Expected behavior)\n"
   "\n"
  +"\n"
  +"\n"
   "> What happened instead? (Actual behavior)\n"
   "\n"
  +"\n"
  +"\n"
   "> What's different between what you expected and what actually happened?\n"
   "\n"
  +"\n"
  +"\n"
   "> Anything else you want to add:\n"
   "\n"
  +"\n"
  +"\n"
   "> Please review the rest of the bug report below.\n"
   "> You can delete any lines you don't wish to share.\n");
   
  diff --git a/t/t0091-bugreport.sh b/t/t0091-bugreport.sh
  index 9d7008f3592..facaf1a5373 100755
  --- a/t/t0091-bugreport.sh
  +++ b/t/t0091-bugreport.sh
  @@ -12,19 +12,32 @@ test_expect_success 'create a report' '
   test_expect_success 'report contains wanted template (before first section)' '
   	sed -ne "/^\[/q;p" git-bugreport-format.txt >actual &&
   	cat >expect <<-\EOF &&
  -	> Thank you for filling out a Git bug report!
  -	> Please answer the following questions to help us understand your issue.
  +	Thank you for filling out a Git bug report!
  +	Please answer the following questions to help us understand your issue.
  +	There are three blank lines after each question; please write your
  +	response on the second line and keep a blank line betweeen the question
  +	and the answer (beginning and end).
   
   	> What did you do before the bug happened? (Steps to reproduce your issue)
   
  +
  +
   	> What did you expect to happen? (Expected behavior)
   
  +
  +
   	> What happened instead? (Actual behavior)
   
  +
  +
   	> What'\''s different between what you expected and what actually happened?
   
  +
  +
   	> Anything else you want to add:
   
  +
  +
   	> Please review the rest of the bug report below.
   	> You can delete any lines you don'\''t wish to share.
   

Range-diff against v2:
1:  52a6177e706 ! 1:  3d00cdbe853 bugreport: use quoted line prefixes
    @@ Metadata
     Author: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
      ## Commit message ##
    -    bugreport: use quoted line prefixes
    +    bugreport: use quoted line prefixes & more blank lines
     
         Quoted line prefixes make it easier to distinguish between the questions
         and the answers, both for the reporter and for the readers.
     
    +    Also try to nudge the user to submit a report with a blank line
    +    separating the end of the question, the answer, and the next
    +    question.[1]  (Or leave optional answers empty, i.e. with three
    +    blank lines.  That should be fine too.)
    +
    +    [1]: Suggested by Junio
    +
         Based-on-patch-by: Felipe Contreras <felipe.contreras@gmail.com>
    +    Suggested-by: Junio C Hamano <gitster@pobox.com>
         Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
     
     
      ## Notes (series) ##
    +    § Changes in v3
    +
    +    • Don’t quote the introduction (not a question and not needed)
    +    • Also try to nudge the user to leave enough blank lines
    +    • Keep using one single patch for less test file churn even though these
    +      are two changes in one
    +
    +    I considered being cute with the footnote:
    +
    +        ...
    +        question.[1] ...
    +
    +        Based-on-patch-by: Felipe Contreras <felipe.contreras@gmail.com>
    +        [1]:
    +        Suggested-by: Junio C Hamano <gitster@pobox.com>
    +        Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
    +
         § Changes in v2
     
         • Update test which wasn’t there when v1 was made
    @@ Notes (series)
         • “use” in the subject is slightly more declarative than “add” (?)
     
      ## builtin/bugreport.c ##
    -@@ builtin/bugreport.c: static const char * const bugreport_usage[] = {
    - static int get_bug_template(struct strbuf *template)
    - {
    +@@ builtin/bugreport.c: static int get_bug_template(struct strbuf *template)
      	const char template_text[] = N_(
    --"Thank you for filling out a Git bug report!\n"
    --"Please answer the following questions to help us understand your issue.\n"
    -+"> Thank you for filling out a Git bug report!\n"
    -+"> Please answer the following questions to help us understand your issue.\n"
    + "Thank you for filling out a Git bug report!\n"
    + "Please answer the following questions to help us understand your issue.\n"
    ++"There are three blank lines after each question; please write your\n"
    ++"response on the second line and keep a blank line betweeen the question\n"
    ++"and the answer (beginning and end).\n"
      "\n"
     -"What did you do before the bug happened? (Steps to reproduce your issue)\n"
     +"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
      "\n"
     -"What did you expect to happen? (Expected behavior)\n"
    -+"> What did you expect to happen? (Expected behavior)\n"
      "\n"
     -"What happened instead? (Actual behavior)\n"
    -+"> What happened instead? (Actual behavior)\n"
      "\n"
     -"What's different between what you expected and what actually happened?\n"
    -+"> What's different between what you expected and what actually happened?\n"
    ++"> What did you expect to happen? (Expected behavior)\n"
      "\n"
     -"Anything else you want to add:\n"
    -+"> Anything else you want to add:\n"
      "\n"
     -"Please review the rest of the bug report below.\n"
     -"You can delete any lines you don't wish to share.\n");
    ++"\n"
    ++"> What happened instead? (Actual behavior)\n"
    ++"\n"
    ++"\n"
    ++"\n"
    ++"> What's different between what you expected and what actually happened?\n"
    ++"\n"
    ++"\n"
    ++"\n"
    ++"> Anything else you want to add:\n"
    ++"\n"
    ++"\n"
    ++"\n"
     +"> Please review the rest of the bug report below.\n"
     +"> You can delete any lines you don't wish to share.\n");
      
    @@ builtin/bugreport.c: static const char * const bugreport_usage[] = {
      	return 0;
     
      ## t/t0091-bugreport.sh ##
    -@@ t/t0091-bugreport.sh: test_expect_success 'create a report' '
    - test_expect_success 'report contains wanted template (before first section)' '
    - 	sed -ne "/^\[/q;p" git-bugreport-format.txt >actual &&
    +@@ t/t0091-bugreport.sh: test_expect_success 'report contains wanted template (before first section)' '
      	cat >expect <<-\EOF &&
    --	Thank you for filling out a Git bug report!
    --	Please answer the following questions to help us understand your issue.
    -+	> Thank you for filling out a Git bug report!
    -+	> Please answer the following questions to help us understand your issue.
    + 	Thank you for filling out a Git bug report!
    + 	Please answer the following questions to help us understand your issue.
    ++	There are three blank lines after each question; please write your
    ++	response on the second line and keep a blank line betweeen the question
    ++	and the answer (beginning and end).
      
     -	What did you do before the bug happened? (Steps to reproduce your issue)
     +	> What did you do before the bug happened? (Steps to reproduce your issue)
      
     -	What did you expect to happen? (Expected behavior)
    -+	> What did you expect to happen? (Expected behavior)
      
     -	What happened instead? (Actual behavior)
    -+	> What happened instead? (Actual behavior)
      
     -	What'\''s different between what you expected and what actually happened?
    -+	> What'\''s different between what you expected and what actually happened?
    ++	> What did you expect to happen? (Expected behavior)
      
     -	Anything else you want to add:
    -+	> Anything else you want to add:
      
     -	Please review the rest of the bug report below.
     -	You can delete any lines you don'\''t wish to share.
    ++
    ++	> What happened instead? (Actual behavior)
    ++
    ++
    ++
    ++	> What'\''s different between what you expected and what actually happened?
    ++
    ++
    ++
    ++	> Anything else you want to add:
    ++
    ++
    ++
     +	> Please review the rest of the bug report below.
     +	> You can delete any lines you don'\''t wish to share.
      

base-commit: 724518f3884d8707c5f51428ba98c115818229b8
-- 
2.50.1

Re: [PATCH v2] bugreport: use quoted line prefixes

[Kristoffer Haugsbakk]

On Fri, Aug 15, 2025, at 18:18, Junio C Hamano wrote:
> kristofferhaugsbakk@fastmail.com writes:
>
>> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>>
>> Quoted line prefixes make it easier to distinguish between the questions
>> and the answers, both for the reporter and for the readers.
>
> This may improve things a bit, but the #1 thing that made the
> reports most hard to read for me, while reading bugreport output
> posted here over time, is lack of a blank line between each question
> and its answer (and the tail end of an answer and the beginning of
> the next question).

I’ve added this in the [v3].

[v3]: <3d00cdbe8535fda8f9e72b5243090e6d953c133e.1755866791.git.code@khaugsbakk.name>

>> -"Thank you for filling out a Git bug report!\n"
>> -"Please answer the following questions to help us understand your issue.\n"
>> +"> Thank you for filling out a Git bug report!\n"
>> +"> Please answer the following questions to help us understand your issue.\n"
>>  "\n"
>
> I do not see a need to quote the above.  Nobody will write in this
> space between the above introductory text and the first question
> below.

I agree.  This has been changed as well in v3.

>
>> -"What did you do before the bug happened? (Steps to reproduce your issue)\n"
>> +"> What did you do before the bug happened? (Steps to reproduce your issue)\n"
>>  "\n"
> [snip]