From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Github Pull Request
Date: Thu, 15 Sep 2022 15:24:24 +0200 [thread overview]
Message-ID: <0bd28c30-fe39-8586-eb2c-0b5dfa65abff@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi All,
Re the question on GitHub Pull Requests from the last conf call.
I have found many people complaining about the fact that you cannot
disable pull requests. Apparently the Linux Kernel also has the problem.
One thing I found suggested is that you can create a Pull Request
Template in GitHub, in which you can write a few words about the fact
that Pull Requests are not accepted and where to look for the approved flow.
Of course people can still ignore those words but then in that case I
would not feel any concern about just deleting those PR's.
Regards,
Adolf.
--
Sent from my laptop
reply other threads:[~2022-09-15 13: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=0bd28c30-fe39-8586-eb2c-0b5dfa65abff@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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