From a39e0857cced03b5c936783c54bfb162e806e41a Mon Sep 17 00:00:00 2001 From: Lucy Macartney Date: Fri, 25 Sep 2026 09:47:37 +0100 Subject: [PATCH 1/6] Add Prettier with format scripts and ignore file Installs prettier as a dev dependency, adds yarn format and yarn format:check, and ignores generated and frozen files. Skills now name the exact command to run. --- .agents/skills/translate/SKILL.md | 3 ++- .agents/skills/update-content/SKILL.md | 5 +++-- .prettierignore | 11 +++++++++++ package.json | 5 ++++- yarn.lock | 10 ++++++++++ 5 files changed, 30 insertions(+), 4 deletions(-) create mode 100644 .prettierignore diff --git a/.agents/skills/translate/SKILL.md b/.agents/skills/translate/SKILL.md index e060e87589e..583a4cedcb4 100644 --- a/.agents/skills/translate/SKILL.md +++ b/.agents/skills/translate/SKILL.md @@ -38,7 +38,8 @@ Check these three things. If any fails, stop and ask. - `glossary.yml` and `translation-rules.yml` are valid YAML. Translate the English page as it is on disk after any fixes and after -Prettier has run, so the hash you record matches what you translated. +`yarn prettier --write ` has run on it, so the hash you record matches +what you translated. ## Front matter diff --git a/.agents/skills/update-content/SKILL.md b/.agents/skills/update-content/SKILL.md index 4b6935d01fe..5bdfaa65495 100644 --- a/.agents/skills/update-content/SKILL.md +++ b/.agents/skills/update-content/SKILL.md @@ -32,8 +32,9 @@ Change docs pages and open a PR. ## Finish Stop when you are done or reach 20 changed files. If work is left, list it in -the PR for the next run. Run Prettier on the files you changed, then build the -site as CI does, which fails on broken links: +the PR for the next run. Format the files you changed with +`yarn prettier --write `, then build the site as CI does, which fails on +broken links: ```bash yarn generate-library diff --git a/.prettierignore b/.prettierignore new file mode 100644 index 00000000000..c1bc19b17c0 --- /dev/null +++ b/.prettierignore @@ -0,0 +1,11 @@ +build/ +.docusaurus/ +node_modules/ +.yarn/ +yarn.lock +adaptors/packages/ +adaptors/library/jobs/auto/ +versioned_docs/ +versioned_sidebars/ +i18n/ +static/ diff --git a/package.json b/package.json index 1212aff46e6..e21d89789c6 100644 --- a/package.json +++ b/package.json @@ -14,7 +14,9 @@ "deploy": "docusaurus deploy", "serve": "docusaurus serve", "clear": "docusaurus clear", - "add-help-sections": "node scripts/add-help-section.js" + "add-help-sections": "node scripts/add-help-section.js", + "format": "prettier --write .", + "format:check": "prettier --check ." }, "dependencies": { "@babel/helper-module-transforms": "^7.17.7", @@ -65,6 +67,7 @@ "@types/react-router-dom": "^5.1.7", "chokidar": "^3.6.0", "glob": "^11.1.0", + "prettier": "3.9.9", "typescript": "~5.2.2" }, "resolutions": { diff --git a/yarn.lock b/yarn.lock index 87de91abe31..ae505f15ebb 100644 --- a/yarn.lock +++ b/yarn.lock @@ -5148,6 +5148,7 @@ __metadata: form-data: 4.0.6 glob: ^11.1.0 mermaid: 11.15.0 + prettier: 3.9.9 prism-react-renderer: ^2.1.0 raw-loader: ^4.0.2 react: ^18.2.0 @@ -14028,6 +14029,15 @@ __metadata: languageName: node linkType: hard +"prettier@npm:3.9.9": + version: 3.9.9 + resolution: "prettier@npm:3.9.9" + bin: + prettier: bin/prettier.cjs + checksum: fbd41978e758c07ce493728c73c9011400446281aca707024e58f7b6ea5ad1dd2f12f8cc51ff76ceb7c7749947db876f6074030a5ec333d8e4084c29455ea948 + languageName: node + linkType: hard + "pretty-error@npm:^4.0.0": version: 4.0.0 resolution: "pretty-error@npm:4.0.0" From 17030322b16c111773ec01802fff941f44637b98 Mon Sep 17 00:00:00 2001 From: Lucy Macartney Date: Fri, 25 Sep 2026 14:14:55 +0100 Subject: [PATCH 2/6] Prettier: ignore only generated and frozen files, format i18n Stop ignoring i18n/ so translations are formatted, as in #848. Ignore all of adaptors/library/ and generate-library/master.temp.json. Drop entries already covered by .gitignore. Format the translate skill. --- .agents/skills/translate/SKILL.md | 123 +++++++++++++++--------------- .prettierignore | 9 +-- 2 files changed, 64 insertions(+), 68 deletions(-) diff --git a/.agents/skills/translate/SKILL.md b/.agents/skills/translate/SKILL.md index 583a4cedcb4..b352c3920c4 100644 --- a/.agents/skills/translate/SKILL.md +++ b/.agents/skills/translate/SKILL.md @@ -11,22 +11,21 @@ disable-model-invocation: true # Translate Translate English docs into Spanish (`es`) and French (`fr`). The English is -always the source of truth. Translations are generated files that live in -this repo. Save each one at the same path as the English page, under +always the source of truth. Translations are generated files that live in this +repo. Save each one at the same path as the English page, under `i18n//docusaurus-plugin-content-docs/current/`. For example, `docs/build/triggers.md` goes to -`i18n/es/docusaurus-plugin-content-docs/current/build/triggers.md`. -Docusaurus ignores a file anywhere else without an error, and the page stays -English. +`i18n/es/docusaurus-plugin-content-docs/current/build/triggers.md`. Docusaurus +ignores a file anywhere else without an error, and the page stays English. -The sidebar headings come from `sidebars-main.js`, not from the pages. If it -has new or renamed entries, run +The sidebar headings come from `sidebars-main.js`, not from the pages. If it has +new or renamed entries, run `yarn docusaurus write-translations --locale `. This adds them to -`i18n//docusaurus-plugin-content-docs/current.json` in English and -keeps the ones already translated. Translate the new ones. +`i18n//docusaurus-plugin-content-docs/current.json` in English and keeps +the ones already translated. Translate the new ones. -Never translate the generated adaptor pages, the job library, the old v1 -docs, or articles and blog posts. +Never translate the generated adaptor pages, the job library, the old v1 docs, +or articles and blog posts. ## Before you start @@ -56,33 +55,32 @@ The hash is the content hash of the English file, from merges: a hash pointing at a commit made on a branch dangles as soon as the branch is squashed onto main. A content hash is the same wherever the file lives, and it answers the only question the field exists to answer: is the -English still the version this was translated from? To compare, hash the -current English file and check it against the recorded value. +English still the version this was translated from? To compare, hash the current +English file and check it against the recorded value. `translation_review_status` can be `machine`, `needs-review`, or -`human-reviewed`. Only a human ever sets `human-reviewed`, and when they do -they also add `translation_reviewer` and `translation_review_date`. +`human-reviewed`. Only a human ever sets `human-reviewed`, and when they do they +also add `translation_reviewer` and `translation_review_date`. ## Decide what to do with each page - **No translation yet.** Translate the whole page. -- **The hash matches the current English file.** Skip it, whatever its - status. The English has not changed since it was translated. The one - exception: if `glossary.yml` or `translation-rules.yml` was committed more - recently than the translation (compare `git log -1 --format=%ct -- `), - treat a `machine` page as if the hash no longer matches, so it picks up the - new rules. -- **The hash no longer matches, and the status is `machine`, `needs-review`, - or missing.** Translate the whole page again, but keep any fenced blocks - (see below) exactly as they were. -- **The hash no longer matches, and the status is `human-reviewed`.** Leave - the file out of the translation PR. Instead, open a separate PR for the - named reviewer that changes only the affected parts. Recover the English the +- **The hash matches the current English file.** Skip it, whatever its status. + The English has not changed since it was translated. The one exception: if + `glossary.yml` or `translation-rules.yml` was committed more recently than the + translation (compare `git log -1 --format=%ct -- `), treat a `machine` + page as if the hash no longer matches, so it picks up the new rules. +- **The hash no longer matches, and the status is `machine`, `needs-review`, or + missing.** Translate the whole page again, but keep any fenced blocks (see + below) exactly as they were. +- **The hash no longer matches, and the status is `human-reviewed`.** Leave the + file out of the translation PR. Instead, open a separate PR for the named + reviewer that changes only the affected parts. Recover the English the reviewer saw with `git cat-file -p `, diff it against the current English, and translate only what changed. In the same PR, set - `translation_source_hash` to the current English hash and leave the status - as `human-reviewed`: the reviewer merging it approves it. If the old version - is no longer in the repo, say so and offer a full retranslation in that PR + `translation_source_hash` to the current English hash and leave the status as + `human-reviewed`: the reviewer merging it approves it. If the old version is + no longer in the repo, say so and offer a full retranslation in that PR instead. ## Fenced blocks @@ -91,19 +89,20 @@ A human can wrap part of a translation like this: ```markdown + Text a reviewer has corrected by hand. ``` Copy those blocks into the new translation exactly, in the same place. If the -English they correspond to has been deleted, keep the block anyway and ask -what to do with it. +English they correspond to has been deleted, keep the block anyway and ask what +to do with it. ## How to translate - Words in `glossary.yml` stay in English. For ordinary words that are also - product terms, like "run" or "step", keep the English only when the word - means the OpenFn thing. + product terms, like "run" or "step", keep the English only when the word means + the OpenFn thing. - Follow any rules for the locale in `translation-rules.yml`. By default, Spanish uses "tú" and French uses "vous". - Copy code blocks and inline code exactly. You may translate comments inside @@ -111,31 +110,31 @@ what to do with it. - Keep the names of things in the app, like buttons, menus, tabs, and field labels, exactly as they are in the English. The app is English only, so a translated button name points the reader at a button that does not exist. -- Keep the same structure: same headings at the same levels, same lists, - same callouts, same components. -- Keep internal links as they are in the English. Do not add `/es/` or - `/fr/`; Docusaurus adds the locale when it builds the page. -- The one exception: a relative link like `../deploy/portability.md` breaks - if the page it points to has no translation yet. Write it as the page's - full address instead, like `/documentation/deploy/portability`. If the - target page sets a `slug` in its front matter, the address is - `/documentation` plus the slug: `slug: /api-tokens` gives - `/documentation/api-tokens`, not the folder path. -- Give translated headings the original English anchor so existing links - still work. +- Keep the same structure: same headings at the same levels, same lists, same + callouts, same components. +- Keep internal links as they are in the English. Do not add `/es/` or `/fr/`; + Docusaurus adds the locale when it builds the page. +- The one exception: a relative link like `../deploy/portability.md` breaks if + the page it points to has no translation yet. Write it as the page's full + address instead, like `/documentation/deploy/portability`. If the target page + sets a `slug` in its front matter, the address is `/documentation` plus the + slug: `slug: /api-tokens` gives `/documentation/api-tokens`, not the folder + path. +- Give translated headings the original English anchor so existing links still + work. ## Before you commit -Check that the fixed glossary terms (the ones without `product_noun: true`, -such as OpenFn, Lightning, adaptor, webhook) appear as many times as in the -English. Product nouns like "run" and "step" are allowed to differ, since -their ordinary-English uses get translated. Before counting, join each file -into one line with single spaces: Prettier wraps prose at 80 columns, and -English and Spanish wrap at different points, so a multi-word term like "work -order" can sit across a line break in one file and not the other. Check the -code blocks are identical. Check the counts of headings, code blocks, -callouts, images, and tables match. Check the front matter is complete. Check -every fenced block survived. Then build the site and make sure it passes: +Check that the fixed glossary terms (the ones without `product_noun: true`, such +as OpenFn, Lightning, adaptor, webhook) appear as many times as in the English. +Product nouns like "run" and "step" are allowed to differ, since their +ordinary-English uses get translated. Before counting, join each file into one +line with single spaces: Prettier wraps prose at 80 columns, and English and +Spanish wrap at different points, so a multi-word term like "work order" can sit +across a line break in one file and not the other. Check the code blocks are +identical. Check the counts of headings, code blocks, callouts, images, and +tables match. Check the front matter is complete. Check every fenced block +survived. Then build the site and make sure it passes: ```bash yarn generate-library @@ -144,11 +143,11 @@ yarn build ``` Build the whole site, not just your locale. `yarn build --locale ` -builds the locale at the site root, so every correct `/es/...` link shows up -as broken. +builds the locale at the site root, so every correct `/es/...` link shows up as +broken. Open one PR per locale, separate from the English PR. Translated files do not -count toward the 20-file limit, because a locale's translations are reviewed -as a set. In the PR description, say which tool and model translated the -pages. If you spot a problem in the English while translating, note it for -the next English pass; do not fix it here. +count toward the 20-file limit, because a locale's translations are reviewed as +a set. In the PR description, say which tool and model translated the pages. If +you spot a problem in the English while translating, note it for the next +English pass; do not fix it here. diff --git a/.prettierignore b/.prettierignore index c1bc19b17c0..91be4172f49 100644 --- a/.prettierignore +++ b/.prettierignore @@ -1,11 +1,8 @@ -build/ -.docusaurus/ -node_modules/ +# Prettier also reads .gitignore, so only list what is committed but must not be reformatted. .yarn/ yarn.lock -adaptors/packages/ -adaptors/library/jobs/auto/ +adaptors/library/ +generate-library/master.temp.json versioned_docs/ versioned_sidebars/ -i18n/ static/ From 5d3285121d03939d75455bf6f64f48813bb18956 Mon Sep 17 00:00:00 2001 From: Lucy Macartney Date: Fri, 25 Sep 2026 14:22:23 +0100 Subject: [PATCH 3/6] Translate skill: keep only the Prettier command change --- .agents/skills/translate/SKILL.md | 123 +++++++++++++++--------------- 1 file changed, 62 insertions(+), 61 deletions(-) diff --git a/.agents/skills/translate/SKILL.md b/.agents/skills/translate/SKILL.md index b352c3920c4..583a4cedcb4 100644 --- a/.agents/skills/translate/SKILL.md +++ b/.agents/skills/translate/SKILL.md @@ -11,21 +11,22 @@ disable-model-invocation: true # Translate Translate English docs into Spanish (`es`) and French (`fr`). The English is -always the source of truth. Translations are generated files that live in this -repo. Save each one at the same path as the English page, under +always the source of truth. Translations are generated files that live in +this repo. Save each one at the same path as the English page, under `i18n//docusaurus-plugin-content-docs/current/`. For example, `docs/build/triggers.md` goes to -`i18n/es/docusaurus-plugin-content-docs/current/build/triggers.md`. Docusaurus -ignores a file anywhere else without an error, and the page stays English. +`i18n/es/docusaurus-plugin-content-docs/current/build/triggers.md`. +Docusaurus ignores a file anywhere else without an error, and the page stays +English. -The sidebar headings come from `sidebars-main.js`, not from the pages. If it has -new or renamed entries, run +The sidebar headings come from `sidebars-main.js`, not from the pages. If it +has new or renamed entries, run `yarn docusaurus write-translations --locale `. This adds them to -`i18n//docusaurus-plugin-content-docs/current.json` in English and keeps -the ones already translated. Translate the new ones. +`i18n//docusaurus-plugin-content-docs/current.json` in English and +keeps the ones already translated. Translate the new ones. -Never translate the generated adaptor pages, the job library, the old v1 docs, -or articles and blog posts. +Never translate the generated adaptor pages, the job library, the old v1 +docs, or articles and blog posts. ## Before you start @@ -55,32 +56,33 @@ The hash is the content hash of the English file, from merges: a hash pointing at a commit made on a branch dangles as soon as the branch is squashed onto main. A content hash is the same wherever the file lives, and it answers the only question the field exists to answer: is the -English still the version this was translated from? To compare, hash the current -English file and check it against the recorded value. +English still the version this was translated from? To compare, hash the +current English file and check it against the recorded value. `translation_review_status` can be `machine`, `needs-review`, or -`human-reviewed`. Only a human ever sets `human-reviewed`, and when they do they -also add `translation_reviewer` and `translation_review_date`. +`human-reviewed`. Only a human ever sets `human-reviewed`, and when they do +they also add `translation_reviewer` and `translation_review_date`. ## Decide what to do with each page - **No translation yet.** Translate the whole page. -- **The hash matches the current English file.** Skip it, whatever its status. - The English has not changed since it was translated. The one exception: if - `glossary.yml` or `translation-rules.yml` was committed more recently than the - translation (compare `git log -1 --format=%ct -- `), treat a `machine` - page as if the hash no longer matches, so it picks up the new rules. -- **The hash no longer matches, and the status is `machine`, `needs-review`, or - missing.** Translate the whole page again, but keep any fenced blocks (see - below) exactly as they were. -- **The hash no longer matches, and the status is `human-reviewed`.** Leave the - file out of the translation PR. Instead, open a separate PR for the named - reviewer that changes only the affected parts. Recover the English the +- **The hash matches the current English file.** Skip it, whatever its + status. The English has not changed since it was translated. The one + exception: if `glossary.yml` or `translation-rules.yml` was committed more + recently than the translation (compare `git log -1 --format=%ct -- `), + treat a `machine` page as if the hash no longer matches, so it picks up the + new rules. +- **The hash no longer matches, and the status is `machine`, `needs-review`, + or missing.** Translate the whole page again, but keep any fenced blocks + (see below) exactly as they were. +- **The hash no longer matches, and the status is `human-reviewed`.** Leave + the file out of the translation PR. Instead, open a separate PR for the + named reviewer that changes only the affected parts. Recover the English the reviewer saw with `git cat-file -p `, diff it against the current English, and translate only what changed. In the same PR, set - `translation_source_hash` to the current English hash and leave the status as - `human-reviewed`: the reviewer merging it approves it. If the old version is - no longer in the repo, say so and offer a full retranslation in that PR + `translation_source_hash` to the current English hash and leave the status + as `human-reviewed`: the reviewer merging it approves it. If the old version + is no longer in the repo, say so and offer a full retranslation in that PR instead. ## Fenced blocks @@ -89,20 +91,19 @@ A human can wrap part of a translation like this: ```markdown - Text a reviewer has corrected by hand. ``` Copy those blocks into the new translation exactly, in the same place. If the -English they correspond to has been deleted, keep the block anyway and ask what -to do with it. +English they correspond to has been deleted, keep the block anyway and ask +what to do with it. ## How to translate - Words in `glossary.yml` stay in English. For ordinary words that are also - product terms, like "run" or "step", keep the English only when the word means - the OpenFn thing. + product terms, like "run" or "step", keep the English only when the word + means the OpenFn thing. - Follow any rules for the locale in `translation-rules.yml`. By default, Spanish uses "tú" and French uses "vous". - Copy code blocks and inline code exactly. You may translate comments inside @@ -110,31 +111,31 @@ to do with it. - Keep the names of things in the app, like buttons, menus, tabs, and field labels, exactly as they are in the English. The app is English only, so a translated button name points the reader at a button that does not exist. -- Keep the same structure: same headings at the same levels, same lists, same - callouts, same components. -- Keep internal links as they are in the English. Do not add `/es/` or `/fr/`; - Docusaurus adds the locale when it builds the page. -- The one exception: a relative link like `../deploy/portability.md` breaks if - the page it points to has no translation yet. Write it as the page's full - address instead, like `/documentation/deploy/portability`. If the target page - sets a `slug` in its front matter, the address is `/documentation` plus the - slug: `slug: /api-tokens` gives `/documentation/api-tokens`, not the folder - path. -- Give translated headings the original English anchor so existing links still - work. +- Keep the same structure: same headings at the same levels, same lists, + same callouts, same components. +- Keep internal links as they are in the English. Do not add `/es/` or + `/fr/`; Docusaurus adds the locale when it builds the page. +- The one exception: a relative link like `../deploy/portability.md` breaks + if the page it points to has no translation yet. Write it as the page's + full address instead, like `/documentation/deploy/portability`. If the + target page sets a `slug` in its front matter, the address is + `/documentation` plus the slug: `slug: /api-tokens` gives + `/documentation/api-tokens`, not the folder path. +- Give translated headings the original English anchor so existing links + still work. ## Before you commit -Check that the fixed glossary terms (the ones without `product_noun: true`, such -as OpenFn, Lightning, adaptor, webhook) appear as many times as in the English. -Product nouns like "run" and "step" are allowed to differ, since their -ordinary-English uses get translated. Before counting, join each file into one -line with single spaces: Prettier wraps prose at 80 columns, and English and -Spanish wrap at different points, so a multi-word term like "work order" can sit -across a line break in one file and not the other. Check the code blocks are -identical. Check the counts of headings, code blocks, callouts, images, and -tables match. Check the front matter is complete. Check every fenced block -survived. Then build the site and make sure it passes: +Check that the fixed glossary terms (the ones without `product_noun: true`, +such as OpenFn, Lightning, adaptor, webhook) appear as many times as in the +English. Product nouns like "run" and "step" are allowed to differ, since +their ordinary-English uses get translated. Before counting, join each file +into one line with single spaces: Prettier wraps prose at 80 columns, and +English and Spanish wrap at different points, so a multi-word term like "work +order" can sit across a line break in one file and not the other. Check the +code blocks are identical. Check the counts of headings, code blocks, +callouts, images, and tables match. Check the front matter is complete. Check +every fenced block survived. Then build the site and make sure it passes: ```bash yarn generate-library @@ -143,11 +144,11 @@ yarn build ``` Build the whole site, not just your locale. `yarn build --locale ` -builds the locale at the site root, so every correct `/es/...` link shows up as -broken. +builds the locale at the site root, so every correct `/es/...` link shows up +as broken. Open one PR per locale, separate from the English PR. Translated files do not -count toward the 20-file limit, because a locale's translations are reviewed as -a set. In the PR description, say which tool and model translated the pages. If -you spot a problem in the English while translating, note it for the next -English pass; do not fix it here. +count toward the 20-file limit, because a locale's translations are reviewed +as a set. In the PR description, say which tool and model translated the +pages. If you spot a problem in the English while translating, note it for +the next English pass; do not fix it here. From 15e53996fb2ed0d3b64dfa1eec02f988471dcf42 Mon Sep 17 00:00:00 2001 From: Lucy Macartney Date: Fri, 25 Sep 2026 15:01:28 +0100 Subject: [PATCH 4/6] Translate skill: format translated files too --- .agents/skills/translate/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.agents/skills/translate/SKILL.md b/.agents/skills/translate/SKILL.md index 583a4cedcb4..9dcec0a1aa9 100644 --- a/.agents/skills/translate/SKILL.md +++ b/.agents/skills/translate/SKILL.md @@ -39,7 +39,8 @@ Check these three things. If any fails, stop and ask. Translate the English page as it is on disk after any fixes and after `yarn prettier --write ` has run on it, so the hash you record matches -what you translated. +what you translated. After writing the translation, run +`yarn prettier --write` on every file you changed under `i18n/`. ## Front matter From ad7f47fd1a8e4190b0bdafc0c3283bf2c8802c03 Mon Sep 17 00:00:00 2001 From: Lucy Macartney Date: Fri, 25 Sep 2026 15:16:19 +0100 Subject: [PATCH 5/6] Translate skill: don't reformat English; ignore glossary and rules files Hash the English page as it is on main so translate never edits docs/. Keep glossary.yml and translation-rules.yml out of Prettier so a reformat commit can't mark every machine translation stale. --- .agents/skills/translate/SKILL.md | 8 ++++---- .prettierignore | 3 +++ 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/.agents/skills/translate/SKILL.md b/.agents/skills/translate/SKILL.md index 9dcec0a1aa9..84019fb1284 100644 --- a/.agents/skills/translate/SKILL.md +++ b/.agents/skills/translate/SKILL.md @@ -37,10 +37,10 @@ Check these three things. If any fails, stop and ask. - `i18n/` is not in `.gitignore`. - `glossary.yml` and `translation-rules.yml` are valid YAML. -Translate the English page as it is on disk after any fixes and after -`yarn prettier --write ` has run on it, so the hash you record matches -what you translated. After writing the translation, run -`yarn prettier --write` on every file you changed under `i18n/`. +Translate the English page exactly as it is on disk, so the hash you record +matches what you translated. Do not reformat it; English changes belong in +their own PR. After writing the translation, run +`yarn prettier --write ` on only the files you changed under `i18n/`. ## Front matter diff --git a/.prettierignore b/.prettierignore index 91be4172f49..3ebda0b42b6 100644 --- a/.prettierignore +++ b/.prettierignore @@ -6,3 +6,6 @@ generate-library/master.temp.json versioned_docs/ versioned_sidebars/ static/ +# Human-maintained; a reformat commit would mark every machine translation stale. +glossary.yml +translation-rules.yml From 8907e5bd14803bfed634ed4ebf27f080d8efccb9 Mon Sep 17 00:00:00 2001 From: Lucy Macartney Date: Fri, 25 Sep 2026 15:19:06 +0100 Subject: [PATCH 6/6] Remove unused format scripts --- package.json | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/package.json b/package.json index 366ed9705f5..47ba52ed131 100644 --- a/package.json +++ b/package.json @@ -14,9 +14,7 @@ "deploy": "docusaurus deploy", "serve": "docusaurus serve", "clear": "docusaurus clear", - "add-help-sections": "node scripts/add-help-section.js", - "format": "prettier --write .", - "format:check": "prettier --check ." + "add-help-sections": "node scripts/add-help-section.js" }, "dependencies": { "@babel/helper-module-transforms": "^7.17.7",