CentOS Stream Kernel Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage
  1. CentOS Stream Kernel Documentation
  2. /
  3. Docs
  4. /
  5. The Format of owners.yaml

The Format of owners.yaml

users: [1]
  - &link [2]
    name: value [3]
    email: value [4]
    gluser: value [5]
    restricted: true / false [6]
subsystems: [7]
  - subsystem: value [8]
    labels: [9]
        name: value [10]
        readyForMergeDeps: [11]
          - value...
    status: value [12]
    devel-sst: [13]
      - value... [14]
    jiraComponent: value [15]
    requiredApproval: true / false [16]
    maintainers: [17]
        - *link... [18]
    reviewers: [19]
        - *link... [20]
    paths: [21]
        includes: [22]
          - value...
        includeRegexes: [23]
          - value...
        excludes: [24]
          - value...
    scm: value [25]
    mailingList: value [26]
    testVariants: [27]
      - value... [28]
1. List of active Red Hat kernel developers.
2. Each user should start with a YAML anchor in the form of &username.
3. Name of the user.
4. Email address of the user.
5. Gitlab username of the user.
6. Whether to exclude the user from the list of required reviewers. Optional.
7. List of kernel Sub System Teams (SSTs).
8. Brief description of the subsystem.
9. Labels added by kernel-webhooks to MRs that are relevant to this subsystem.
10. Brief name of the subsystem, used to derive Subsystem:{name} label and approval rule name.
11. List of ExternalCI:: labels that will be assigned to relevant MRs. Optional.
12. Red Hat support status of this subsystem. Allowed values: Supported, Provided, Internal, Disabled, Unassigned.
13. List of Red Hat Engineering SSTs that are responsible for developing this subsystem.
14. Allowed values: rhel-sst-accelerators, rhel-ssg-arr, rhel-sst-arch-hw, rhel-sst-cee-supportability, rhel-sst-centos-stream, rhel-sst-cki, rhel-sst-cloudexperience, rhel-sst-cockpit, rhel-sst-container-tools, rhel-sst-cpe, rhel-sst-cpt, rhel-sst-cs-apps, rhel-sst-cs-infra-services, rhel-sst-cs-plumbers, rhel-sst-cs-software-management, rhel-sst-cs-system-management, rhel-sst-desktop, rhel-sst-desktop-applications, rhel-sst-desktop-firmware-bootloaders, rhel-sst-desktop-platform-technologies, rhel-sst-edge, rhel-sst-filesystems, rhel-sst-gpu, rhel-sst-high-availability, rhel-sst-i18n, rhel-sst-idm-cs, rhel-sst-idm-ds, rhel-sst-idm-hms, rhel-sst-idm-ipa, rhel-sst-idm-ops, rhel-sst-idm-sssd, rhel-sst-image-builder, rhel-sst-installer, rhel-sst-kernel-debug, rhel-sst-kernel-ft, rhel-sst-kernel-maintainers, rhel-sst-kernel-rts, rhel-sst-kernel-security, rhel-sst-kernel-tps, rhel-sst-kernel-tps-gitlab, rhel-sst-logical-storage, rhel-sst-network-drivers, rhel-sst-network-fastdatapath, rhel-sst-networking-core, rhel-sst-osci, rhel-sst-packit, rhel-sst-pt-gcc-glibc, rhel-sst-pt-llvm-rust-go, rhel-sst-pt-pcp, rhel-sst-pt-perf-debug, rhel-sst-rh-ceph-storage, rhel-sst-rhcos, rhel-sst-security-compliance, rhel-sst-security-crypto, rhel-sst-security-readiness, rhel-sst-security-selinux, rhel-sst-security-special-projects, rhel-sst-storage-io, rhel-sst-storage-management, rhel-sst-subscription-manager, rhel-sst-system-roles, rhel-sst-upgrades, rhel-sst-virtualization, rhel-sst-virtualization-advanced, rhel-sst-virtualization-cloud, rhel-sst-virtualization-hwe, rhel-sst-virtualization-networking, rhel-sst-virtualization-spice, rhel-sst-virtualization-storage, rhel-sst-virtualization-windows, rhivos-ft-auto-kernel, rhivos-ft-cats, RHEL-SST-Conversions, security-compliance-team.
15. RHEL jira project component that should be set when filing issues against this subsystem.
16. Whether a relevant MR must get an approval from a maintainer or a reviewer of this subsystem before it can be merged. Optional.
17. List of maintainers for this subsystem. The developers listed here are the primary contact for the subsystem. Must have at least one.
18. Each maintainer must be specified by a YAML alias to the users top level section.
19. List of additional reviewers for this subsystem. Optional.
20. Each reviewer must be specified by a YAML alias to the users top level section.
21. Paths matched to identify MRs relevant to this subsystem. Although optional, in practice, at least one path should be specified. Optional.
22. List of files and directories to include. Can contain shell-like wildcard patterns. Optional.
23. List of files and directories regex patterns to include. Optional.
24. List of files and directories to exclude. Can contain shell-like wildcard patterns. Optional.
25. SCM tree type and location string. Type is one of git, hg, quilt, stgit. The type and location is separated by a space. Optional.
26. Mailing list for the subsystem. Optional.
27. List of kernel variants that should be tested when a file in paths is changed for this subsystem. Optional.
28. Allowed values: kernel-rt, kernel-64k, kernel-automotive.
gdoc_arrow_left_alt Bugzilla Lifecycle Owners Yaml Principles gdoc_arrow_right_alt