On 22/07/2026 11:55, Claudio Bantaloukas wrote: > ChangeLog: > > * .github/CONTRIBUTING.md: Update text. > * .github/PULL_REQUEST_TEMPLATE.md: Link > to CONTRIBUTING.md directly. > --- > We currently use two files that warn users of github trying to make pull > requests against gcc mirrors that their efforts will not be rewarded. > > Rather than just tell them to use email, offer them a choice between that and > using the forge. > > .github/CONTRIBUTING.md | 26 ++++++++++++-------------- > .github/PULL_REQUEST_TEMPLATE.md | 6 +----- > 2 files changed, 13 insertions(+), 19 deletions(-) > mode change 100644 => 120000 .github/PULL_REQUEST_TEMPLATE.md > > diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md > index d218924bf9d..799d7d92771 100644 > --- a/.github/CONTRIBUTING.md > +++ b/.github/CONTRIBUTING.md > @@ -1,24 +1,22 @@ > ## 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. > +Thanks for taking the time to contribute to GCC! > + > +Please be advised that all mirrors on `github.com` are unofficial and > unmonitored. > + > The GCC community does not use `github.com` for their contributions. > Instead, we use > a mailing list (`[email protected]`) for code submissions, code > -reviews, and bug reports. > +reviews, and bug reports. A guide for those unfamiliar with the process can > be > +found on 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" wiki > page](https://gcc.gnu.org/wiki/GettingStarted). > > -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. > +In addition, the GCC project uses a [forgejo > instance](https://forge.sourceware.org/gcc/gcc) > +to enable contributors to submit pull requests for review. These pull > requests > +are not automatically merged, they are sent to the mailing list via > automation for you, > +and can be reviewed either on the forge or on the mailing list itself. > +To make use of this, follow the instruction in the ["Using > Forge"](https://gcc.gnu.org/wiki/UsingForge) page. > > 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 > deleted file mode 100644 > index 6417392c8cf..00000000000 > --- a/.github/PULL_REQUEST_TEMPLATE.md > +++ /dev/null > @@ -1,5 +0,0 @@ > -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 (`[email protected]`) for code submissions, code > reviews, and > -bug reports. Please send patches there instead. > diff --git a/.github/PULL_REQUEST_TEMPLATE.md > b/.github/PULL_REQUEST_TEMPLATE.md > new file mode 120000 > index 00000000000..eada936c1d5 > --- /dev/null > +++ b/.github/PULL_REQUEST_TEMPLATE.md > @@ -0,0 +1 @@ > +CONTRIBUTING.md > \ No newline at end of file
I'm not entirely sure about this last bit. The GCC sources do not currently create any symlinks on checkout and I'm not sure how portable this is to systems other than linux (not all Windows filesystems support it, IIRC). Perhaps we could have a shorter text entry that references CONTRIBUTING.md instead? R.
