public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io, nathaniel.l.desimone@intel.com
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Merge commit in edk2-non-osi
Date: Wed, 21 Feb 2024 09:57:47 +0100	[thread overview]
Message-ID: <283c01e7-7f41-4db4-93cc-532e97bbd20b@linaro.org> (raw)
In-Reply-To: <MW4PR11MB5821A4386082053AF891B650CD572@MW4PR11MB5821.namprd11.prod.outlook.com>

W dniu 21.02.2024 o 2:49 AM, Nate DeSimone pisze:

> I would like to remind everyone that we generally don't accept
> submissions via PRs yet. At the very least please click "Rebase and
> merge" when closing the PR instead of "Merge pull request". Since that
> merge commit is currently at the top of the tree, can we delete it?

You can configure repository on github to not have merge commits on PR 
merge. Settings allow to choose and you can leave 'allow rebase merging' 
as the only option.

Pull requests functionality cannot be disabled but there are pages 
describing how to reply and close/reject automatically.


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



  parent reply	other threads:[~2024-02-21  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  1:49 [edk2-devel] Merge commit in edk2-non-osi Nate DeSimone
2024-02-21  8:06 ` Ard Biesheuvel
2024-02-21 15:05   ` Michael D Kinney
2024-02-21 23:29     ` Ard Biesheuvel
2024-02-21 23:42       ` Nate DeSimone
2024-02-21  8:57 ` Marcin Juszkiewicz [this message]
2024-02-21 15:26   ` Michael D Kinney

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=283c01e7-7f41-4db4-93cc-532e97bbd20b@linaro.org \
    --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