From: John Snow <jsnow@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: FYI GitHub pull request / issue tracker lockdown bot
Date: Mon, 6 Apr 2020 15:51:52 -0400 [thread overview]
Message-ID: <b321b36e-d18f-623b-f8a1-93bd4b3fb779@redhat.com> (raw)
In-Reply-To: <20200403142213.GO559148@redhat.com>
On 4/3/20 10:22 AM, Daniel P. Berrangé wrote:
> QEMU, like libvirt, has a github.com project which contains automated
> read-only mirrors of QEMU repositories.
>
> https://github.com/qemu/
>
> An unfortunate side effect of this is that some users will try to open
> pull requests against these mirrors. These get ignored until eventually
> someone notices and closes the request. QEMU has had about 90 prs opened
> over the years.
>
> https://github.com/qemu/qemu/pulls
>
> The same applies to the issue tracker, but fortunately github lets
> projects disable this feature, which QEMU has done.
>
> I have recently discovered that there is a nice 3rd party bot for github
> which can autorespond to pull requests with a friendly comment, close the
> request, and then lock it to prevent further comments.
>
> https://github.com/apps/repo-lockdown
>
> I'm setting this up for libvirt and it was suggested QEMU can probably
> benefit from it too as an example see:
>
> https://github.com/libvirt/test/issues/2
> https://github.com/libvirt/test/pull/3
>
>
> Configuration just requires creation of a ".github/lockdown.yml" file
> which provides the friendly message to add to the merge requests. This
> can be either done per-repository, or a special repo can be created
> called ".github" and this will apply to all repos within the project.
>
> Ideally each repo would have a CONTRIBUTING.md file created too, since
> both GitHub and GitLab will direct users to this file for guidelines
> on how to contribute.
>
> I don't have time right now to do this for QEMU, so consider this email
> a friendly suggestion for some other interested person to do for QEMU...
>
> Regards,
> Daniel
>
This looks cool. Who has access to our github to request it start
scanning our repo to look for said .github/lockdown.yml file?
--js
next prev parent reply other threads:[~2020-04-06 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 14:22 FYI GitHub pull request / issue tracker lockdown bot Daniel P. Berrangé
2020-04-06 19:51 ` John Snow [this message]
2020-04-07 8:47 ` Daniel P. Berrangé
2020-04-22 16:01 ` Stefan Hajnoczi
2020-04-22 17:35 ` Paolo Bonzini
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=b321b36e-d18f-623b-f8a1-93bd4b3fb779@redhat.com \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).