##
## CODEOWNERS style rules:
## 1. Prefer team ownership over individual user ownership.
## 2. GBT-related team should be listed first.
## 3. Try to keep paths alphabetically sorted within visual groups.
## 4. List individual owners last.
##

# bt-unassigned-maintainers must be the first owner
# All directories that are not explicitly listed below are considered

                // We should not include the root variant's dependencies in the locally accessible set
                locallyAccessible.add(to.owner)
            }
            is ModuleComponentIdentifier -> externallyAccessible.add(to.owner)
        }

        if (seen.add(to)) {
            dependency.selected.getDependenciesForVariant(to).forEach {
                queue.add(it)
            }
        }

 * @returns {[Object]} Returns a list of objects for each platform containing info about the changes to files in that platform
 * @example {{ owners | categorize(branch.diff.files_metadata) }}
 */

function categorize(fileOwners, fileMetadatas) {
    const result = new Map();
    [...fileOwners.keys()].forEach(platform => {
        result.set(platform, {

enabled.set('includes_todos', ['community', 'tresat']);
enabled.set('javadoc_on_new_files', ['community', 'tresat']);
enabled.set('lacks_tests', ['community', 'tresat']);
enabled.set('summary_table_owners', ['tresat']);
enabled.set('summary_table_platforms', ['community', 'tresat']);

// Require Opt-In/User Request
enabled.set('code_experts', []);

// Always run
enabled.set('add_usual_expert', ['always']);

 *
 * @param {[Object]} statistics - list of summary data objects from computeStatistics
 * @param {String} title - description of how data is grouped
 * @returns {String} Returns the formatted HTMl table string.
 * @example {{ owners | categorize(branch.diff.files_metadata) | computeStatistics(branch.diff.files_metadata) | summaryTable('Platform') }}
 */
function summaryTable(statistics, title) {

description: Create a report to help us improve
labels: [ "a:bug", "to-triage" ]
assignees: [ ]
body:
  - type: markdown
    attributes:
      value: |
        Please follow the instructions below.
        We receive dozens of issues every week, so to stay productive, we will close issues that don't provide enough information.

An architecture module is responsible for providing a coherent set of features and:

- Provides a set of APIs and services for use from outside the module.
- Has a private implementation.
- Is owned by a single team. A team may own multiple architecture modules.

The modules are arranged into several different "Gradle platforms".
A Gradle platform is a logical distribution that provides support for a specific kind of automation.

        files.map(f => {
            console.log("Resolving owners for: " + f);
            const owners = resolveCodeowners(mapping, f);
            console.log("Owners for: " + f + " are: " + owners);
            owners.filter(i => typeof i === 'string')
                .map(u => u.replace(/^@gradle\//, ""))
                .forEach(owner => {
                    if (!result.has(owner)) {
                        result.set(owner, []);

 * @description Groups the PR's files by platform based on the file's path.
 * @param {string[]} files - the gitStream's files context variable
 * @returns {Map} - Map from platform to list of files in this PR in it
 * @example {{ owners | byPlatform }}
 */
function byPlatform(files) {
    const result = new Map();
    files.forEach(file => {
        const platform = getPlatform(file);
        if (!result.has(platform)) {