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
The PR formatter should be updated to check that these instructions have been followed:
Replace this text with an actual descrption:
<_Include a description of the change and why this change was made._>
Remove this line of instructions so the PR description shows cleanly in release notes:
"For details on how to complete to complete these options and their meaning refer to [CONTRIBUTING.md](https://github.com/microsoft/mu/blob/HEAD/CONTRIBUTING.md)."
For each checkbox in the PR description, place an "x" in between [ and ] if true. Example: [x]. (you can also check items in the GitHub UI)
[] Impacts functionality?
Functionality - Does the change ultimately impact how firmware functions?
Examples: Add a new library, publish a new PPI, update an algorithm, ...
[] Impacts security?
Security - Does the change have a direct security impact on an application,
flow, or firmware?
The Mu DevOps PR Formatting Validator workflow validates correct formatting of PR descriptions in Project Mu repos.
The PR formatter should be updated to check that these instructions have been followed:
Replace this text with an actual descrption:
Remove this line of instructions so the PR description shows cleanly in release notes:
"For details on how to complete to complete these options and their meaning refer to [CONTRIBUTING.md](https://github.com/microsoft/mu/blob/HEAD/CONTRIBUTING.md)."
For each checkbox in the PR description, place an "x" in between
[
and]
if true. Example:[x]
.(you can also check items in the GitHub UI)
flow, or firmware?
validation improvement, ...
in build or boot behavior?
a function in a new library class in a pre-existing module, ...
outside direct code modifications (and comments)?
on an a separate Web page, ...
Replace this text as instructed:
Replace this text with as instructed:
The text was updated successfully, but these errors were encountered: