public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@bsdio.com" <rebecca@bsdio.com>,
	Michael Kubacki <mikuback@linux.microsoft.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] GitHub PRs and Mergify: " Allow edits from maintainers" needs to be enabled
Date: Mon, 17 Jun 2024 16:35:45 +0000	[thread overview]
Message-ID: <CO1PR11MB492989DC3B40BD629809442ED2CD2@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB49294AC983221F2815AFB96DD2CD2@CO1PR11MB4929.namprd11.prod.outlook.com>

Hi Rebecca,

I see you have already attempted this.

I read the message/docs.  Perhaps the right thing to do here is for
contributors to change that setting.

What is strange is that the GitHub option to rebase the branch is also
not available, and it usually is.

Mike

> -----Original Message-----
> From: Kinney, Michael D <michael.d.kinney@intel.com>
> Sent: Monday, June 17, 2024 9:29 AM
> To: devel@edk2.groups.io; rebecca@bsdio.com; Michael Kubacki
> <mikuback@linux.microsoft.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: RE: [edk2-devel] GitHub PRs and Mergify: " Allow edits from
> maintainers" needs to be enabled
> 
> I highlighted this issue in a summary before.
> 
> When this is seen, a Maintainer need to request a rebase.
> 
> Mike
> 
> > -----Original Message-----
> > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> > Sent: Monday, June 17, 2024 8:43 AM
> > To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>;
> > Michael Kubacki <mikuback@linux.microsoft.com>
> > Subject: [edk2-devel] GitHub PRs and Mergify: " Allow edits from
> maintainers"
> > needs to be enabled
> >
> > I'm having problems merging https://github.com/tianocore/edk2/pull/5774
> > - Mergify reports:
> >
> >
> > The merge queue pull request can't be updated
> > Details:
> >
> >     Pull request can't be updated with latest base branch changes
> >
> >     Mergify needs the author permission to update the base branch of the
> >     pull request.
> >     @Beckhoff <https://github.com/Beckhoff> needs to authorize
> >     modification on its head branch
> >     <https://docs.github.com/en/pull-requests/collaborating-with-pull-
> > requests/working-with-forks/allowing-changes-to-a-pull-request-branch-
> > created-from-a-fork>.
> >
> >
> > It looks like we need to require users creating PRs to enable the "Allow
> > edits from maintainers" settin*g?*
> > *
> > *
> > *--
> > Rebecca Cran
> > *
> >
> >
> >
> > 
> >



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119595): https://edk2.groups.io/g/devel/message/119595
Mute This Topic: https://groups.io/mt/106723083/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2024-06-17 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 15:42 [edk2-devel] GitHub PRs and Mergify: " Allow edits from maintainers" needs to be enabled Rebecca Cran
2024-06-17 16:29 ` Michael D Kinney
2024-06-17 16:35   ` Michael D Kinney [this message]

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=CO1PR11MB492989DC3B40BD629809442ED2CD2@CO1PR11MB4929.namprd11.prod.outlook.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