n8n:community-pr-readiness-check

Source excerpt starting at line 1.

1# Community PR Readiness Check — teams and labels2 3Owner resolution, the GitHub-team → Linear-team → label mapping, and the Linear ticket label rules used when triaging.4 5## Contents6 7- Identifying the owning team8- GitHub team → Linear team → GitHub label9- Linear ticket label rules10  - Always-on label11  - Type label (based on PR title prefix)12  - Team-specific extra label13  - Worked examples14 15---16 17## Identifying the owning team18 19Use the canonical owners script at `.github/scripts/owners.mjs`. It parses `.github/OWNERS` with last-match-wins semantics and returns allocations sorted by file count with a `share` percentage. Using the script keeps this skill consistent with whatever CI uses.20 211. Write the PR's changed file paths (from the `files` list) to a temp file, one per line:22   ```bash23   printf '%s\n' <path1> <path2> ... > /tmp/pr-<number>-files.txt24   ```252. Run the script:26   ```bash27   node .github/scripts/owners.mjs /tmp/pr-<number>-files.txt28   ```293. The script prints JSON of the form:30   ```json31   {32     "totalFiles": 12,33     "allocations": [34       { "team": "@n8n-io/ai", "fileCount": 10, "share": 83, "files": [...] },35       { "team": "@n8n-io/catalysts", "fileCount": 2, "share": 17, "files": [...] }36     ]37   }38   ```39   Allocations are already sorted by `fileCount` descending — take the first entry as the winning team.404. Clean up: `rm /tmp/pr-<number>-files.txt`.415. Strip the `@n8n-io/` prefix from `allocations[0].team` — the GitHub team slug is `nodes`, `iam`, `ai`, etc. If `allocations` is empty (no file matched any rule, which is possible only if `.github/OWNERS` lost its catch-all), fall back to `catalysts`.426. Map the GitHub team slug to its Linear team name and PR label using the table below. The `team` field in the JSON output is the **Linear team name**. If the resolved GitHub team slug has no entry in the table, fall back to `Engineering`.43 44**Sub-agent fallback**: if `node` execution is denied by the sandbox, read `.github/OWNERS` directly and apply last-match-wins by hand. All the active rules fit on one screen.45 46## GitHub team → Linear team → GitHub label47 48| GitHub team (`@n8n-io/…`) | Linear team             | GitHub team label  |49|---------------------------|-------------------------|--------------------|50| `catalysts`               | Catalysts               | `team:cats`        |51| `adore`                   | Adore                   | `team:adore`       |52| `ai`                      | AI                      | `team:ai`          |53| `nodes`                   | NODES                   | `team:nodes`       |54| `design`                  | Design                  | `team:design`      |55| `iam`                     | Identity & Access       | `team:identity`    |56| `ligo`                    | Lifecycle & Governance  | `team:lifecycle`   |57| `ai-assistant`            | AI Assistant            | `team:instance-ai` |58| `frontend`                | Adore                   | `team:adore`       |59| `qa-dx`                   | Developer Platform      | `team:qa-dx`       |60| `migrations-review`       | Catalysts               | `team:cats`        |61 62The **GitHub team label** column is what gets applied to the PR after a successful Linear assignment (see `reference/label-flow.md`).63 64## Linear ticket label rules65 66When calling the available Linear MCP issue-update tool to assign a ticket to a team, pass a `labels` array composed of three pieces:67 68### Always-on label69 70- `GitHub` — every community PR ticket carries this. In the Linear UI it renders as `source > GitHub`; the `source` prefix is a label-group parent, not part of the API name.71 72### Type label (from PR title prefix)73 74| PR title type                                                                          | Linear label   |75|----------------------------------------------------------------------------------------|----------------|76| `feat`                                                                                 | `feature`      |77| `fix`                                                                                  | `bug`          |78| anything else (`perf`, `refactor`, `docs`, `ci`, `chore`, `build`, `test`, `revert`)   | `enhancement`  |79 80Pass the **child** label name only — Linear silently drops unknown labels, so don't include `type > ` prefixes.81 82### Team-specific extra label83 84| Destination team | Extra label    |85|------------------|----------------|86| Catalysts        | `Community PR` |87| NODES            | `community-pr` |88| other teams      | _(no extra)_   |89 90### Worked examples91 92- `feat` PR going to Catalysts: `["GitHub", "feature", "Community PR"]`93- `fix` PR going to NODES: `["GitHub", "bug", "community-pr"]`94- `perf` PR going to AI: `["GitHub", "enhancement"]`95- `chore` PR going to Lifecycle & Governance: `["GitHub", "enhancement"]`96 97## Destination state98 99| Destination team | Linear state |100|------------------|--------------|101| NODES            | `Review`     |102| any other team   | `Triage`     |103 104NODES has a dedicated `Review` lane; every other team handles routing inside their own triage.105 106This same table governs the **issue-ticket** state move when a ready PR is linked onto a referenced issue ticket (SKILL.md step 7B): move the issue ticket to `Review` for NODES, `Triage` otherwise — keyed off the PR's resolved owner team.107