Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: DongdongZhang <zhangdongdong@eswincomputing.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	bonet@grenoble.cnrs.fr, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] .github: add github action to automate PR handling
Date: Mon, 8 Jul 2024 22:29:33 +0200	[thread overview]
Message-ID: <20240708222933.5a0fd505@windsurf> (raw)
In-Reply-To: <1a197586.4af8.1909028b645.Coremail.zhangdongdong@eswincomputing.com>

Hello,

On Mon, 8 Jul 2024 10:25:05 +0800 (GMT+08:00)
DongdongZhang <zhangdongdong@eswincomputing.com> wrote:

> > Can probably just use a github script along these lines or something:
> > https://github.com/sbabic/swupdate/blob/2024.05.2/.github/workflows/contributing.yml
> > 
> > probably also needs a conditional so it only runs on the one github repo:
> > if: github.repository == ‘buildroot/buildroot’
> >   
> 
> Hi, James,
> In this scenario, I believe that using `dessant/repo-lockdown@v4` is more suitable 
> than `actions/github-script@v5`. `dessant/repo-lockdown@v4` is specifically focused 
> on repository lockdown functionality and has been widely used and validated. 
> In contrast, while `actions/github-script@v5` is flexible, it requires more 
> customization and maintenance work and a strong familiarity with JavaScript. 
> To keep the process simple and stable, I have decided to continue 
> using `dessant/repo-lockdown@v4`.

I do agree with you on this. However, you didn't reply to the second
comment from James, on checking that the action only runs on the main
buildroot repo, and not others. Indeed, we don't want people/companies
forking our repo to have this PR lockdown action triggered.

Could you check this, and send an updated version of your patch?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-08 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08  1:37 [Buildroot] [PATCH v2 0/1] .github: add github action to automate PR handling zhangdongdong
2024-07-08  1:37 ` [Buildroot] [PATCH v2 1/1] " zhangdongdong
2024-07-08  2:13   ` James Hilliard
2024-07-08  2:25     ` DongdongZhang
2024-07-08 20:29       ` Thomas Petazzoni via buildroot [this message]
2024-07-09  1:40         ` DongdongZhang

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=20240708222933.5a0fd505@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bonet@grenoble.cnrs.fr \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=zhangdongdong@eswincomputing.com \
    /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