public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Eric Gallager <egallager@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/egallager/heads/github-notices)] Add files to discourage submissions of PRs to the GitHub mirror.
Date: Mon, 16 Oct 2023 23:24:49 +0000 (GMT)	[thread overview]
Message-ID: <20231016232449.3EAF23858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:249e2144c36dd22b59bde9ee52333b27e5b7055c

commit 249e2144c36dd22b59bde9ee52333b27e5b7055c
Author: Eric Gallager <egallager@gcc.gnu.org>
Date:   Mon Oct 16 19:22:17 2023 -0400

    Add files to discourage submissions of PRs to the GitHub mirror.
    
    ChangeLog:
    
            * .github/CONTRIBUTING.md: New file.
            * .github/PULL_REQUEST_TEMPLATE.md: New file.

Diff:
---
 .github/CONTRIBUTING.md          | 18 ++++++++++++++++++
 .github/PULL_REQUEST_TEMPLATE.md |  5 +++++
 2 files changed, 23 insertions(+)

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
new file mode 100644
index 000000000000..4f7b3abca5f4
--- /dev/null
+++ b/.github/CONTRIBUTING.md
@@ -0,0 +1,18 @@
+## Contributing to GCC
+
+Thanks for taking the time to contribute to GCC! Please be advised that if you are
+viewing this on `github.com`, that the mirror there is unofficial and unmonitored.
+The GCC community does not use `github.com` for their contributions. Instead, we use
+a mailing list (`gcc-patches@gcc.gnu.org`) for code submissions, code
+reviews, and bug reports.
+
+Perhaps one day it will be possible to use [GitGitGadget](https://gitgitgadget.github.io/) to
+conveniently send Pull Requests commits to GCC's mailing list, the way that the Git project currently allows it to be used to send PRs to their mailing list, but until that day arrives, please send your patches to the mailing list manually.
+
+Please read ["Contributing to GCC"](https://gcc.gnu.org/contribute.html) on the main GCC website
+to learn how the GCC project is managed, and how you can work with it.
+In addition, we highly recommend you to read [our guidelines for read-write Git access](https://gcc.gnu.org/gitwrite.html).
+
+Or, you can follow the ["Contributing to GCC in 10 easy steps"](https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps) section of the ["Getting Started" page](https://gcc.gnu.org/wiki/GettingStarted) on [the wiki](https://gcc.gnu.org/wiki) for another example of the contribution process.
+
+Your friendly GCC community!
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000000..6417392c8cf3
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,5 @@
+Thanks for taking the time to contribute to GCC! Please be advised that if you are
+viewing this on `github.com`, that the mirror there is unofficial and unmonitored.
+The GCC community does not use `github.com` for their contributions. Instead, we use
+a mailing list (`gcc-patches@gcc.gnu.org`) for code submissions, code reviews, and
+bug reports. Please send patches there instead.

                 reply	other threads:[~2023-10-16 23:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231016232449.3EAF23858D37@sourceware.org \
    --to=egallager@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).