You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #299 updated .sync/workflows/leaf/codeql.yml to first check the new location (as of Mu 2311) for the CodeQL plugin in Mu Basecore BaseTools. If not found, it falls back to the previous location in .pytools.
This is to allow immediate backward compatibility with the latest Mu DevOps release across existing Mu branches. It is recommended that 2302 (and other relevant branches) move to the BaseTools location. When all branches are confirmed to have moved, the fallback to .pytools can be removed in the file.
The text was updated successfully, but these errors were encountered:
… BaseTools (#299)
The CodeQL plugin moved from .pytool to BaseTools in the Mu Basecore
202311 update. This change first looks for the plugin in BaseTools and
falls back to the prior .pytool location if it is not found for backward
compatibility with some earlier release branches that have not picked up
the change.
Eventually, the .pytool fallback can be removed.
---
Issue to track removal of the fallback:
#300
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
PR #299 updated
.sync/workflows/leaf/codeql.yml
to first check the new location (as of Mu 2311) for the CodeQL plugin in Mu Basecore BaseTools. If not found, it falls back to the previous location in .pytools.This is to allow immediate backward compatibility with the latest Mu DevOps release across existing Mu branches. It is recommended that 2302 (and other relevant branches) move to the BaseTools location. When all branches are confirmed to have moved, the fallback to .pytools can be removed in the file.
The text was updated successfully, but these errors were encountered: