Labels
Labels
124 labels
- Categorizes an issue or PR as actively needing an API review.
- Denotes an issue or PR intended to be handled by the code of conduct committee.
- Denotes an issue or PR intended to be handled by the product security committee.
- Denotes an issue or PR intended to be handled by the steering committee.
- Pull requests that update a dependency file
- Documentation requirements for deprecation/removal of components or APIs.
- DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
- Indicates that a PR should not merge because it touches files in blocked paths.
- Indicates that a PR is not yet approved to merge into a release branch.
- Indicates a PR which contains merge commits.
- Indicates that a PR should not merge because someone has issued a /hold command.
- Do not merge this PR. It is still being reviewed.
- Indicates that a PR should not merge because it has an invalid commit message.
- Indicates that a PR should not merge because it has an invalid OWNERS file in it.
- Indicates a PR lacks a `kind/foo` label and requires one.
- Indicates an issue or PR lacks a `sig/foo` label and requires one.
- Indicates that a PR should not merge because it's missing one of the release note labels.
- Indicates that a PR should not merge because it is a work in progress.
- This item is related to the Lyshine and 2D renderer subsystems.
- This item is related to the EmotionFX animation subsystem.
- This item is related to AR or VR features.
- This item is related to the asset-processor subsystem.
- This item is related to the ATOM and 3D rendering subsystems.
- This item is related to the audio subsystem.
- This item is related to the AZ core engine support libraries.
- Content relating to CMake or the overall build system of O3DE.
- This item is related to the cloud services.
- This item is related to the editor subsystem.
- Content relating to the Gem system of O3DE.
- This item is related to the client or server network code.