From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: [edk2-devel] PRs with issues reported by CodeQL
Date: Sun, 26 Jan 2025 17:39:50 +0000 [thread overview]
Message-ID: <CO1PR11MB49290B8404E5C90439D2040AD2ED2@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
EDK II Maintainers and Reviewers,
If a PR has an issue that is added by a CodeQL scan, and that
issue is later resolved by code updates to the PR, the PR will
not be merged by Mergify.
The reason is that the state of the conversation started by
CodeQL is not seen as resolved by Mergify, even though CodeQL
believes it is resolved. This issue has been reported, but there
is no date for a fix yet.
This has impacted a handful of PRs since it was first observed a
couple months ago.
There are 2 options to merge a PR in this state.
1) [Recommended] Maintainer reopens the specific conversation
opened by CodeQL and adds a comment that the issue is now
resolved and then closes the conversation as resolved. The
PR is now merged because Mergify sees all conversations as
resolved.
Example:
https://github.com/tianocore/edk2/pull/10617#discussion_r1929813777
2) Close the current PR and open a new PR with the state of
code that does not have any Code QL issues. Complete reviews
of the new PR and it will be merged after 'push' label set.
Best regards,
Mike
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121045): https://edk2.groups.io/g/devel/message/121045
Mute This Topic: https://groups.io/mt/110825057/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2025-01-26 17:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CO1PR11MB49290B8404E5C90439D2040AD2ED2@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