Repository navigation
docs: add the DEPLOY namespace to the error reference - #377
quicksilversel wants to merge 1 commit into
Conversation
The deploy pipeline's errors print docsUrls that point at this page, but the page had no DEPLOY section, so every such link dead-ended. Adds the namespace table row and one entry per code the mounted Composer family raises, with text taken from the envelopes' own message, why and fix fields. Signed-off-by: quicksilversel <quicksilversel@gmail.com>
|
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title names the change: adding a DEPLOY namespace to the error reference doc. The raw summary confirms the namespace row, the DEPLOY section, and the 14 documented codes all match this title. The … |
| Description check | |
The description explains the problem and the change. DEPLOY.* errors print a docsUrl that resolves to this page, but the page lacked a DEPLOY section. It states the change adds a namespace table row a… |
| Docstring Coverage | |
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Title check
-
Explanation
The title names the change: adding a DEPLOY namespace to the error reference doc. The raw summary confirms the namespace row, the DEPLOY section, and the 14 documented codes all match this title. The title is specific and short, and it uses the docs: prefix convention.
Full details: Description check
-
Explanation
The description explains the problem and the change. DEPLOY.* errors print a docsUrl that resolves to this page, but the page lacked a DEPLOY section. It states the change adds a namespace table row and a DEPLOY section with 14 codes, and that the change is Markdown-only. This matches the changeset described in the raw summary.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
✨ Simplify code
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
Every
DEPLOY.*error prints a docsUrl that resolves to this page, but the page had noDEPLOYsection, so the links dead-ended. Hit in practice throughDEPLOY.PREFLIGHT_FAILED(prisma/composer#394), whose printed docs link leads nowhere.docs/reference/error-reference.md: aDEPLOYrow in the namespace table and aDEPLOYsection betweenCLIandDEV, with one entry per code the mounted Composer family raises (14 codes, enumerated from@prisma/composerand@prisma/composer-prisma-cloud0.35.0). Entry text follows each envelope's own message, why and fix fields, and the format mirrors the existing family-maintainedDEVentries.Validation
pnpm check:error-referenceverifies codes from this repository's source, so added family entries do not affect it.