From: DongdongZhang <zhangdongdong@eswincomputing.com>
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: 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 10:25:05 +0800 (GMT+08:00) [thread overview]
Message-ID: <1a197586.4af8.1909028b645.Coremail.zhangdongdong@eswincomputing.com> (raw)
In-Reply-To: <CADvTj4r-1xVwmr+W=Lyj2Ff4KZMR8znZyuAgguCt24Y46oYhkg@mail.gmail.com>
> -----原始邮件-----发件人:"James Hilliard" <james.hilliard1@gmail.com>发送时间:2024-07-08 10:13:30 (星期一)收件人:zhangdongdong@eswincomputing.com抄送:buildroot@buildroot.org, bonet@grenoble.cnrs.fr主题:Re: [Buildroot] [PATCH v2 1/1] .github: add github action to automate PR handling
>
> On Sun, Jul 7, 2024 at 7:38 PM <zhangdongdong@eswincomputing.com> wrote:
> >
> > From: Dongdong Zhang <zhangdongdong@eswincomputing.com>
> >
> > This patch updates the Buildroot repository's GitHub configuration to better
> > manage incoming pull requests.
> >
> > - Added a new GitHub Actions workflow (`repo-lockdown.yml`) to automatically
> > handle new pull requests.
> >
> > The new workflow:
> > - Triggers on new pull requests.
> > - Uses the `dessant/repo-lockdown` action to:
> > - Comment on the pull request, guiding contributors to use the mailing list
> > for patch submission.
> > - Lock the pull request to prevent further discussion.
> > - Close the pull request.
> >
> > This change ensures that contributors are properly directed to the preferred
> > method of patch submission via the mailing list, maintaining consistency and
> > streamlining the review process.
> >
> > Signed-off-by: Dongdong Zhang <zhangdongdong@eswincomputing.com>
> > ---
> > .github/workflows/repo-lockdown.yml | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> > create mode 100644 .github/workflows/repo-lockdown.yml
> >
> > diff --git a/.github/workflows/repo-lockdown.yml b/.github/workflows/repo-lockdown.yml
> > new file mode 100644
> > index 0000000000..a5f8bd6a93
> > --- /dev/null
> > +++ b/.github/workflows/repo-lockdown.yml
> > @@ -0,0 +1,23 @@
> > +name: 'Repo Lockdown'
> > +
> > +on:
> > + pull_request_target:
> > + types: opened
> > +
> > +permissions:
> > + pull-requests: write
> > +
> > +jobs:
> > + action:
> > + runs-on: ubuntu-latest
> > + steps:
> > + - uses: dessant/repo-lockdown@v4
>
> 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`.
Thank you again for your suggestion.
> > + with:
> > + pr-comment: |
> > + Please do not submit a Pull Request via GitHub. Buildroot makes use of a
> > + [mailing list](http://lists.buildroot.org/mailman/listinfo/buildroot) for patch submission and review.
> > + See [submitting your own patches](http://buildroot.org/manual.html#submitting-patches) for more info.
> > +
> > + Thanks for your help!
> > + lock-pr: true
> > + close-pr: true
> > \ No newline at end of file
> > --
> > 2.17.1
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-08 2:27 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 [this message]
2024-07-08 20:29 ` Thomas Petazzoni via buildroot
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=1a197586.4af8.1909028b645.Coremail.zhangdongdong@eswincomputing.com \
--to=zhangdongdong@eswincomputing.com \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.