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.

Sign up for GitHub

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

Jump to bottom

cmd/go/internal/bug: sync issue body format with GitHub template #28583

Closed
dmitshur opened this issue Nov 4, 2018 · 2 comments
Closed

cmd/go/internal/bug: sync issue body format with GitHub template #28583

dmitshur opened this issue Nov 4, 2018 · 2 comments
Labels
FrozenDueToAge GoCommand cmd/go NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. release-blocker
Milestone
Go1.12

Comments

@dmitshur
Copy link
Contributor

dmitshur commented Nov 4, 2018 •
edited

I've made a proposal to modify the GitHub issue template in #27914. It was accepted and recently implemented in CL 138295. /cc @andybons

From what I've seen so far in the last few days, it has lead to better formatting of issue reports and increased their readability.

If others are equally happy with it, we should backport it to the format that the go bug command uses, so they're in sync:

go/src/cmd/go/internal/bug/bug.go

Lines 72 to 86 in 6fe8ee7

const bugHeader = `Please answer these questions before submitting your issue. Thanks!
#### What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
#### What did you expect to see?
#### What did you see instead?
`

go/.github/ISSUE_TEMPLATE

Lines 3 to 36 in 6fe8ee7

### What version of Go are you using (`go version`)?
<pre>
$ go version
</pre>
### Does this issue reproduce with the latest release?
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
</pre></details>
### What did you do?
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
### What did you expect to see?
### What did you see instead?

There's no rush on this, as the implementation is trivial, as long as the decision is made before 1.12.
@dmitshur dmitshur added NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. GoCommand cmd/go labels Nov 4, 2018
@dmitshur dmitshur added this to the Go1.12 milestone Nov 4, 2018
@myitcv
Copy link
Member

myitcv commented Nov 4, 2018

@dmitshur FYI https://go-review.googlesource.com/c/go/+/127495

@joshblakeley - probably a good time to finish up your changes in that CL :)

@dmitshur
Copy link
Contributor Author

dmitshur commented Nov 4, 2018

Thanks Paul. I think I can close this issue as duplicate of #26751 then.

@dmitshur dmitshur closed this as completed Nov 4, 2018
@dmitshur dmitshur mentioned this issue Nov 4, 2018
Closed
@golang golang locked and limited conversation to collaborators Nov 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge GoCommand cmd/go NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. release-blocker
Projects
None yet
Milestone
Go1.12
Development

No branches or pull requests
3 participants
@dmitshur @myitcv @gopherbot