diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md deleted file mode 100644 index 2b4a5fccdaf12f..00000000000000 --- a/.github/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,3 +0,0 @@ -# Code of Conduct - -Please read the [Go Community Code of Conduct](https://golang.org/conduct). diff --git a/.github/ISSUE_TEMPLATE b/.github/ISSUE_TEMPLATE deleted file mode 100644 index 5cbfc09fe76804..00000000000000 --- a/.github/ISSUE_TEMPLATE +++ /dev/null @@ -1,38 +0,0 @@ - - -### What version of Go are you using (`go version`)? - -
-$ go version
-
-
- -### Does this issue reproduce with the latest release? - - - -### What operating system and processor architecture are you using (`go env`)? - -
go env Output
-$ go env
-
-
- -### What did you do? - - - - - -### What did you expect to see? - - - -### What did you see instead? diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE deleted file mode 100644 index 2e978b61380862..00000000000000 --- a/.github/PULL_REQUEST_TEMPLATE +++ /dev/null @@ -1,25 +0,0 @@ -This PR will be imported into Gerrit with the title and first -comment (this text) used to generate the subject and body of -the Gerrit change. - -**Please ensure you adhere to every item in this list.** - -More info can be found at https://github.com/golang/go/wiki/CommitMessage - -+ The PR title is formatted as follows: `net/http: frob the quux before blarfing` - + The package name goes before the colon - + The part after the colon uses the verb tense + phrase that completes the blank in, - "This change modifies Go to ___________" - + Lowercase verb after the colon - + No trailing period - + Keep the title as short as possible. ideally under 76 characters or shorter -+ No Markdown -+ The first PR comment (this one) is wrapped at 76 characters, unless it's - really needed (ASCII art, table, or long link) -+ If there is a corresponding issue, add either `Fixes #1234` or `Updates #1234` - (the latter if this is not a complete fix) to this comment -+ If referring to a repo other than `golang/go` you can use the - `owner/repo#issue_number` syntax: `Fixes golang/tools#1234` -+ We do not use Signed-off-by lines in Go. Please don't add them. - Our Gerrit server & GitHub bots enforce CLA compliance instead. -+ Delete these instructions once you have read and applied them diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md deleted file mode 100644 index 23fec84fb65e3b..00000000000000 --- a/.github/SUPPORT.md +++ /dev/null @@ -1,14 +0,0 @@ -Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions. -We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://golang.org/s/proposal-process). - -For asking questions, see: - -* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts) - -* [The Go Forum](https://forum.golangbridge.org/), a web-based forum - -* [Gophers Slack](https://gophers.slack.com), use the [invite app](https://invite.slack.golangbridge.org/) for access - -* [Stack Overflow](https://stackoverflow.com/questions/tagged/go) with questions tagged "go" - -* **IRC** channel #go-nuts on Freenode