Skip to content

Labels

Labels

162 labels

  • committee/code-of-conduct

    committee/code-of-conduct
    Denotes an issue or PR intended to be handled by the code of conduct committee.

  • committee/product-security

    committee/product-security
    Denotes an issue or PR intended to be handled by the product security committee.

  • committee/steering

    committee/steering
    Denotes an issue or PR intended to be handled by the steering committee.

  • dependencies

    dependencies
    Pull requests that update a dependency file

  • deprecated

    deprecated
    Documentation requirements for deprecation/removal of components or APIs.

  • do-not-merge/blocked-paths

    do-not-merge/blocked-paths
    Indicates that a PR should not merge because it touches files in blocked paths.

  • do-not-merge/cherry-pick-not-approved

    do-not-merge/cherry-pick-not-approved
    Indicates that a PR is not yet approved to merge into a release branch.

  • do-not-merge/contains-merge-commits

    do-not-merge/contains-merge-commits
    Indicates a PR which contains merge commits.

  • do-not-merge/hold

    do-not-merge/hold
    Indicates that a PR should not merge because someone has issued a /hold command.

  • do-not-merge/hold-from-release

    do-not-merge/hold-from-release
    Indicates a PR must remain in `development` only and must not go into `main` or `stabilization`

  • do-not-merge/in-review

    do-not-merge/in-review
    Do not merge this PR. It is still being reviewed.

  • do-not-merge/invalid-commit-message

    do-not-merge/invalid-commit-message
    Indicates that a PR should not merge because it has an invalid commit message.

  • do-not-merge/invalid-owners-file

    do-not-merge/invalid-owners-file
    Indicates that a PR should not merge because it has an invalid OWNERS file in it.

  • do-not-merge/needs-kind

    do-not-merge/needs-kind
    Indicates a PR lacks a `kind/foo` label and requires one.

  • do-not-merge/needs-sig

    do-not-merge/needs-sig
    Indicates a PR lacks a `sig/foo` label and requires one.

  • do-not-merge/work-in-progress

    do-not-merge/work-in-progress
    Indicates that a PR should not merge because it is a work in progress.

  • do-not-merge/wrong-base-branch

    do-not-merge/wrong-base-branch
    Indicates a PR that wants to be merged into the wrong originating branch

  • feature-need/awaiting-more-evidence

    feature-need/awaiting-more-evidence
    Feature: Unknown importance. Possibly useful but not yet enough evidence to actually get it done

  • feature-need/immediate

    feature-need/immediate
    Feature: Immediate. Must be actively worked on as someone's top priority right now.

  • feature-need/important-longterm

    feature-need/important-longterm
    Feature: Important over the long term but may not be staffed May need multiple releases to complete

  • feature-need/important-soon

    feature-need/important-soon
    Feature: Must be staffed / worked on either currently or very soon ideally in time for next release

  • feature/2d-renderer

    feature/2d-renderer
    This item is related to the 2D renderer subsystems.

  • feature/ai

    feature/ai
    This item is related to the AI feature.

  • feature/animation

    feature/animation
    This item is related to the EmotionFX animation subsystem.

  • feature/ar-vr

    feature/ar-vr
    This item is related to AR or VR features.

  • feature/asset-pipeline

    feature/asset-pipeline
    This item is related to the asset-pipeline subsystem.

  • feature/atom

    feature/atom
    This item is related to the ATOM and 3D rendering subsystems.

  • feature/audio

    feature/audio
    This item is related to the audio subsystem.

  • feature/azcore

    feature/azcore
    This item is related to the AZ core engine support libraries.

  • feature/bluejay

    feature/bluejay
    Categorizes issue or PR as related to the Bluejay Design System.