24 Feb 21:04

v0.1.1 Latest

Latest

What's Changed

remove edk2-basetools @Javagedes (#162)
Change Details
## Description
Removes edk2-basetools from pip-requirements.txt and any usage of it in the CISettings.py. The is done as there are changes in the build tools python source code that are available locally in BaseTools (as is managed by Project Mu) that is not available in edk2-basetools.
- 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?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- Breaking change?
  - Breaking change - Will anyone consuming this change experience a break
    in build or boot behavior?
  - Examples: Add a new library class, move a module to a different repo, call
    a function in a new library class in a pre-existing module, ...
- Includes tests?
  - Tests - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
  - Documentation - Does the change contain explicit documentation additions
    outside direct code modifications (and comments)?
  - Examples: Update readme file, add feature readme file, link to documentation
    on an a separate Web page, ...
How This Was Tested

Verified the build system continues to use the local python source

Integration Instructions

N/A - only effects this repository's CI system.
```
  </blockquote>
  <hr>
</details>
```

Remove old CodeQL GitHub workflow @makubacki (#159)
Change Details
## Description
The leaf workflow from Mu Devops is not synced to this repo right
now, so it is using an old version of the CodeQL workflow that has
not been updated.

Due to the permission change, this version will not function without
permissions being added. For now, the workflow can just be removed
and replaced with the current version when needed later.
- 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?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- Breaking change?
  - Breaking change - Will anyone consuming this change experience a break
    in build or boot behavior?
  - Examples: Add a new library class, move a module to a different repo, call
    a function in a new library class in a pre-existing module, ...
- Includes tests?
  - Tests - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
  - Documentation - Does the change contain explicit documentation additions
    outside direct code modifications (and comments)?
  - Examples: Update readme file, add feature readme file, link to documentation
    on an a separate Web page, ...
How This Was Tested
- Repo CI.
Integration Instructions

N/A - Only affects workflows run on GitHub.

Update pip-requirements.txt @Javagedes (#156)
Change Details
## Description
Updates edk2-pytool-extensions and edk2-pytool-library to work with the latest commit of MU_BASECORE

For each item, 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?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- Breaking change?
  - Breaking change - Will anyone consuming this change experience a break
    in build or boot behavior?
  - Examples: Add a new library class, move a module to a different repo, call
    a function in a new library class in a pre-existing module, ...
- Includes tests?
  - Tests - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- Includes documentation?
  - Documentation - Does the change contain explicit documentation additions
    outside direct code modifications (and comments)?
  - Examples: Update readme file, add feature readme file, link to documentation
    on an a separate Web page, ...
How This Was Tested

N/A

Integration Instructions

N/A
```
  </blockquote>
  <hr>
</details>
```

Full Changelog: v0.1.0...v0.1.1

Contributors

makubacki and Javagedes

Assets 2

22 Jun 15:35

v0.1.0

What's Changed

Remove files in prep for file syncing @makubacki (#43)
Change Details
## Description
1. Removes the PR template from the old location (repo root). File sync
  will track this file in the .github directory now.
2. Removes issue templates. Issue forms will be auto synced from mu_devops
  now.
- Breaking change?
  - Will this change break pre-existing builds or functionality without action being taken?
    No
How This Was Tested

Code review.

Integration Instructions

N/A

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

Remove pull\_request trigger for add-to-project GitHub action @makubacki (#31)

Change Details

## Description
Closes #32

Since GitHub treats workflows triggered from forks (and Dependabot) as
untrusted, they receive a read-only GITHUB_TOKEN and the PRs cannot
access any secrets in the repository.

A secret token is required with project write access for the add-to-project
action to automatically assign issues and PRs to a project.

More information:
https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/

The trigger type could be changed to pull_request_target which would
grant permission to the secret token:
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target

But that has security implications as described here:
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/

In the end, we'll just remove the action for pull requests for now and only have
issues automatically get assigned to the project upon creation.

How This Was Tested

Verified actions/add-to-project no longer triggers on pull requests.

Integration Instructions

N/A

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

Add Project automation workflow @makubacki (#25)

Change Details

## Description
Closes #24

Adds a workflow to use the add-to-project GitHub action.

The project-automation.yml file added in this change does not do any filtering so
all new issues and pull requests will automatically be added to the
"Project Mu UEFI Variables" project.

The Project URL is:
https://github.com/orgs/microsoft/projects/479

How This Was Tested

Verified GitHub action in PR.

Integration Instructions

N/A

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

VariablePkg: Compile something to placate CodeQL @makubacki (#26)

Change Details

## Description
Adds a minimal amount of source code to compile so CodeQL can find build output and not produce an error.

The component built in this change can be removed when another actual component is added.

How This Was Tested

Verified CI build locally.
Verified CodeQL GitHub action in PR results.

Integration Instructions

N/A

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

VariablePkg: Add initial package @makubacki (#20)
Change Details
## Description
Closes #5

Adds an empty package that builds successfully.

This provides a foundation for future code changes and allows CI to be put in place around the build.

How This Was Tested
1. Verified the following commands return successfully:
  1. stuart_ci_setup -c .pytool/CISettings.py
  2. stuart_update -c .pytool/CISettings.py
  3. stuart_ci_build -c .pytool/CISettings.py
  4. stuart_update -c .pytool/CISettings.py -p VariablePkg
2. Verified build with build command: build -p VariablePkg -a IA32 -a X64 -t VS2022
Integration Instructions

VariablePkg can be brought into a consumer repo as a dependency now but that is not very
useful as the package is not populated yet.

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

🚀 Features & ✨ Enhancements

Enable Stale and Label Sync Workflows [Rebase \& FF] @makubacki (#42)

Change Details

- Adds a workflow to identify stale PRs and issues - Adds a workflow to sync GitHub labels
See commit messages for details.

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

Add initial design document @makubacki (#3)

Change Details

## Description
Closes #22

This document proposes an initial set of design guidance in
preparation for a starting implementation.

How This Was Tested

Error free in markdownlint.

Integration Instructions

N/A

📖 Documentation Updates

Add initial design document @makubacki (#3)

Change Details

## Description
Closes #22

This document proposes an initial set of design guidance in
preparation for a starting implementation.

How This Was Tested

Error free in markdownlint.

Integration Instructions

N/A

ReadMe.rst: Add initial file @makubacki (#2)

Change Details

## Description
Adds the initial readme file for the repo.

It currently provides some background on the project, the
TianoCore UEFI variable driver, and some brief contribution
and code of conduct information.

How This Was Tested

Verified restructured text output in GitHub preview

Integration Instructions

N/A - Read the file to gain a better understanding of the repo

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

Full Changelog: ...v0.1.0

Contributors

makubacki

Assets 2