| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | blog: clean up blog to allow usage with gcloud command | Andrew Bonventre | 2018-05-24 |
| | | | | | | | | | | | | | | | | | | + The app.yaml file needs to be in the same directory as the entry-point Go files, so those are moved from ./blog to ./ + Go files within the context article did not have the +build OMIT directive, so gcloud would view them as files that needed to be built at deploy time. Add the +build OMIT directive and use the context package instead of x/net/context. + Switch to using a service instead of version and update app.yaml to account for this. + Use 1.9 as the runtime. + Remove superfluous .gitignore Change-Id: I7c886849b912bc7f5b67cd2791cb6986d93d5cc7 Reviewed-on: https://go-review.googlesource.com/114455 Reviewed-by: Russ Cox <rsc@golang.org> | ||
| * | README, template: add more links | Kevin Burke | 2017-07-17 |
| Move the README to README.md so Gerrit can render it; currently Gerrit only renders files named exactly "README.md" (for example at https://go.googlesource.com/go). Add more links to the README explaining how to file issues, how to submit code changes, where to download the code to and how to get it. Hopefully this should help people who go to https://go.googlesource.com/blog or https://github.com/golang/blog figure out how to get started with development. Add a link in the footer to the source code for the blog, so people know where to find it. Updates golang/go#21038. Updates golang/go#21034. Change-Id: Ie378cf2aa42f56485b5d5c9a943f5b9957d96371 Reviewed-on: https://go-review.googlesource.com/49291 Reviewed-by: Russ Cox <rsc@golang.org> | |||