mu_oem_sample/.gitignore

/Build/
.DS_Store
*_extdep/
*.pyc
__pycache__/
tags/
.vscode/
*.bak
BuildConfig.conf

# Ignore cloned dependencies
/Common
/Features
/Silicon
/MU_BASECORE

_TEMP_*/
/Conf/
Sync pipelines and requirements with Basecore 2020-10-08 06:39:57 +03:00			`/Build/`
Create a dev/201905 branch and update CI build definition and settings 2019-08-23 00:15:48 +03:00			`.DS_Store`
Sync pipelines and requirements with Basecore 2020-10-08 06:39:57 +03:00			`*_extdep/`
Create a dev/201905 branch and update CI build definition and settings 2019-08-23 00:15:48 +03:00			`*.pyc`
Sync pipelines and requirements with Basecore 2020-10-08 06:39:57 +03:00			`__pycache__/`
			`tags/`
			`.vscode/`
Create a dev/201905 branch and update CI build definition and settings 2019-08-23 00:15:48 +03:00			`*.bak`
			`BuildConfig.conf`

			`# Ignore cloned dependencies`
			`/Common`
Remove the data library and introduce the metadata policy (#109) # Preface Please ensure you have read the [contribution docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior to submitting the pull request. In particular, [pull request guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices). ## Description This change pairs with the latest update from mu_feature_config, where it starts to host the data library definition. The configuration policy creator module is also updated to consume the newly created `gProfileFlavorNames` to demonstrate the usage of such data. For each item, place an "x" in between `[` and `]` if true. Example: `[x]`. _(you can also check items in the GitHub UI)_ - [x] 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 This was tested on QEMU Q35 and SBSA platforms. ## Integration Instructions N/A 2023-06-22 23:35:40 +03:00			`/Features`
Create a dev/201905 branch and update CI build definition and settings 2019-08-23 00:15:48 +03:00			`/Silicon`
			`/MU_BASECORE`
Sync pipelines and requirements with Basecore 2020-10-08 06:39:57 +03:00
Create a dev/201905 branch and update CI build definition and settings 2019-08-23 00:15:48 +03:00			`_TEMP_*/`
Sync pipelines, requirements, and documents with Basecore 2021-03-24 17:57:16 +03:00			`/Conf/`