blog
blog copied to clipboard
golang
added a trivial case that can save developers time in quick onboarding
Hi,
I just wanted to add this trivial case for future developers to ensure smoother on boarding.
I have mentioned further details in https://github.com/golang/go/issues/40427
This PR (HEAD: dee005b8e5075f56a417bbbf0c6205b0b43e8fd5) has been imported to Gerrit for code review.
Please visit https://go-review.googlesource.com/c/blog/+/245161 to see it.
Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info
Message from Gobot Gobot:
Patch Set 1:
Congratulations on opening your first change. Thank you for your contribution!
Next steps: A maintainer will review your change and provide feedback. See https://golang.org/doc/contribute.html#review for more info and tips to get your patch through code review.
Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.
Please don’t reply on this GitHub thread. Visit golang.org/cl/245161. After addressing review feedback, remember to publish your drafts!
Message from Go Bot:
Patch Set 1:
Congratulations on opening your first change. Thank you for your contribution!
Next steps: A maintainer will review your change and provide feedback. See https://golang.org/doc/contribute.html#review for more info and tips to get your patch through code review.
Most changes in the Go project go through a few rounds of revision. This can be surprising to people new to the project. The careful, iterative review process is our way of helping mentor contributors and ensuring that their contributions have a lasting impact.
Please don’t reply on this GitHub thread. Visit golang.org/cl/245161. After addressing review feedback, remember to publish your drafts!
This PR is being closed because golang.org/cl/245161 has been abandoned.
Closing because the content of x/blog moved to x/website (see CL 324270). If this change still applies, it'd need to be re-sent it to x/website. Thanks.