Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Justin Bronder <jsbronder@cold-front.org>
To: richard.purdie@linuxfoundation.org
Cc: alex.kanavin@gmail.com,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>,
	",openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	yocto-status@lists.yoctoproject.org
Subject: Re: Yocto Project Status 11 Feb. 2025 (WW07)
Date: Thu, 13 Feb 2025 14:13:11 -0500	[thread overview]
Message-ID: <Z65ER5YO6Ci2MAK0@ravine.members.linode.com> (raw)
In-Reply-To: <d22a4cec5e317e62f1f44d8d9a810cf4745ccb48.camel@linuxfoundation.org>

On 11/02/25 23:36 +0000, Richard Purdie via lists.openembedded.org wrote:
> You used to be able to disable pull requests for six month periods, it
> looks like you can no longer do that and it was a pain having to try
> and remember anyway.

Isn't this just 'Settings -> Moderation Options -> Interaction Limits'?  It looks like you can restrict it to repository collaborators (which is a list under the repo owner's control) to 6 months.

It's also exposed on the REST API, https://docs.github.com/en/rest/interactions/repos?apiVersion=2022-11-28#set-interaction-restrictions-for-a-repository, which if you're willing to pull down the official github cli tool, gh, could go into a cron job fairly easily:

gh api -X PUT \
    /repos/openembedded/openembedded-core/interaction-limits \
    -f 'limit=collaborators_only' \
    -f 'expiry=six_months'

I obviously couldn't test in the OpenEmbedded Org, but this worked both on my personal repos and in a private (paid) organization.

-- 
Justin Bronder


  parent reply	other threads:[~2025-02-13 19:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 15:57 Yocto Project Status 11 Feb. 2025 (WW07) Stephen K Jolley
2025-02-11 18:42 ` [OE-core] " Alexander Kanavin
2025-02-11 23:36   ` Richard Purdie
2025-02-12  8:08     ` [yocto] " Yoann Congal
2025-02-12  9:38       ` Alexander Kanavin
2025-02-12  9:46         ` Richard Purdie
2025-02-12  9:51       ` Richard Purdie
2025-02-12 11:19         ` Yoann Congal
2025-02-12 23:03           ` Yoann Congal
2025-02-13  8:48             ` Alexander Kanavin
2025-02-13  9:18               ` Yoann Congal
2025-02-13  9:45               ` Richard Purdie
2025-02-13  9:50                 ` Alexander Kanavin
2025-02-13  9:52                   ` Yoann Congal
2025-02-13  9:54                     ` Alexander Kanavin
2025-02-13 10:03                       ` Richard Purdie
2025-02-13 10:09                         ` Alexander Kanavin
2025-02-13 11:16                         ` Yoann Congal
2025-02-13 19:13     ` Justin Bronder [this message]
2025-02-13 21:37       ` Yoann Congal

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=Z65ER5YO6Ci2MAK0@ravine.members.linode.com \
    --to=jsbronder@cold-front.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto-status@lists.yoctoproject.org \
    --cc=yocto@lists.yoctoproject.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