From: "Laszlo Ersek" <lersek@redhat.com>
To: "Rabeda, Maciej" <maciej.rabeda@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Wu, Jiaxin" <jiaxin.wu@intel.com>,
Maciej Rabeda <maciej.rabeda@linux.intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>
Cc: "Fu, Siyuan" <siyuan.fu@intel.com>
Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address
Date: Tue, 10 Dec 2019 13:36:45 +0100 [thread overview]
Message-ID: <077c152f-22f8-ce29-ccaa-10874d5e8381@redhat.com> (raw)
In-Reply-To: <BYAPR11MB3527C4B94DD483857508DAA7F95B0@BYAPR11MB3527.namprd11.prod.outlook.com>
On 12/10/19 10:32, Rabeda, Maciej wrote:
> Laszlo,
>
> Understood, Jiaxin and I have successfully went with one patch via PR flow already.
> I was wondering whether any extra actions are required so that I will be able to apply 'push' label to my/other contributor's pull requests to tianocore/edk2.
Important detail: at this stage, we are not dealing with github.com pull
requests from *others*. Only following use cases are in scope:
(1) maintainer submits a PR, or reopen a PR they submitted earlier, for
the purposes of a personal CI build (no "push" label)
(2) same as (1), except with the "push" label set, for the purposes of
an actual fast-forward merge (not just personal CI build); with the
topic branch that's subject to the merge consisting purely of patches
that have been posted *and reviewed* earlier on the list.
(3) same as (1), except with "non-maintainer contributor" replacing
"maintainer"
A PR, submitted by anyone for the edk2 project on github.com, such that
it does not fall in any of the above categories, should be rejected,
just like before. Patch submission and review continues on the mailing list.
To put differently, you should *only* set the push label on a PR that:
- you have submitted / reopened yourself; and
- the topic branch subject to the merge consists only of patches that
you authored, or applied from others from the list, *and* have been
reviewed on the list; and
- the topic branch subject to the merge carries all the feedback tags
given on the list (such as Tested-by, Acked-by, Reviewed-by).
Basically, as a maintainer, you need to:
- follow the list,
- once there are approved patches for NetworkPkg, pick them up with
"git-am" in a local topic branch,
- rebase the local topic branch with "git-rebase", so you can apply the
R-b / T-b / A-b tags from the list to the commit messages,
- push the above topic branch to your own github repo,
- submit a PR for the topic branch,
- set the "push" label on the PR.
"pick up patches from the list" and "pick up feedback tags from the
list" are *not* optional.
> I assume that the list of people that can apply that label is limited to EDK II Maintainers or is my assumption wrong?
Technically, anyone can create a pull request, and my understanding is
that anyone can set the "push" label on their pull request.
However (AIUI), the mergify bot will reject and close any PR with the
"push" label set if the PR was not submitted by a maintainer in the
first place.
Thanks
Laszlo
next prev parent reply other threads:[~2019-12-10 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 16:28 [PATCH] Maintainers.txt: Update reviewer email address Maciej Rabeda
2019-12-10 5:37 ` Wu, Jiaxin
2019-12-10 8:35 ` [edk2-devel] " Rabeda, Maciej
2019-12-10 9:10 ` Laszlo Ersek
2019-12-10 9:32 ` Rabeda, Maciej
2019-12-10 12:36 ` Laszlo Ersek [this message]
2019-12-10 15:01 ` Rabeda, Maciej
2019-12-10 18:15 ` Laszlo Ersek
2019-12-10 18:16 ` Laszlo Ersek
2019-12-10 18:27 ` Michael D Kinney
2019-12-10 22:05 ` Rabeda, Maciej
2019-12-10 10:27 ` Philippe Mathieu-Daudé
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-list 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=077c152f-22f8-ce29-ccaa-10874d5e8381@redhat.com \
--to=devel@edk2.groups.io \
/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