Remove .pytool CodeQL fallback in the CodeQL workflow

Open
#300 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

Open .sync/workflows/leaf/codeql.yml and review the current plugin lookup and its .pytools fallback. Confirm that relevant branches have moved to the Mu Basecore BaseTools location, then remove the fallback while preserving the new lookup behavior. Verify the CodeQL workflow still resolves the plugin from the new location.

Written by the indexing model from the issue text.

Description

state:backlog

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.

Dominant language
Dockerfile
Stars
43
Forks
36
Avg merge
1d 23h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/mu_devops

All issues in microsoft/mu_devops

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.