Fix prettier configs

.woodpecker/docs.yaml

@@ -37,15 +37,26 @@ when:
     evaluate: 'TASK == "docs"'
 
 steps:
-  prettier:
-    image: docker.io/woodpeckerci/plugin-prettier:next
-    settings:
-      version: 3.3.3
-      plugins:
-        - 'prettier-plugin-tailwindcss'
-        - '@ianvs/prettier-plugin-sort-imports'
+  install-dependencies:
+    image: *node_image
+    directory: docs/
+    commands:
+      - corepack enable
+      - pnpm install --frozen-lockfile
     when:
-      - event: pull_request
+      - path: *when_path
+        event: [tag, pull_request, push]
+      - event: manual
+
+  format-check:
+    image: *node_image
+    directory: docs/
+    commands:
+      - corepack enable
+      - pnpm format:check
+    when:
+      - path: *when_path
+        event: pull_request
 
   build-cli:
     image: *golang_image
@@ -61,7 +72,6 @@ steps:
     directory: docs/
     commands:
       - corepack enable
-      - pnpm install --frozen-lockfile
       - pnpm build
     when:
       - path: *when_path

.woodpecker/static.yaml

@@ -23,7 +23,4 @@ steps:
     pull: true
     depends_on: []
     settings:
-      version: 3.3.3
-      plugins:
-        - 'prettier-plugin-tailwindcss'
-        - '@ianvs/prettier-plugin-sort-imports'
+      version: 3.6.2

.woodpecker/web.yaml

@@ -24,18 +24,6 @@ steps:
       - pnpm install --frozen-lockfile
     when: *when
 
-  prettier:
-    depends_on:
-      - install-dependencies
-    image: docker.io/woodpeckerci/plugin-prettier:next
-    pull: true
-    settings:
-      version: 3.3.3
-      plugins:
-        - 'prettier-plugin-tailwindcss'
-        - '@ianvs/prettier-plugin-sort-imports'
-    when: *when
-
   lint:
     depends_on:
       - install-dependencies

docs/.prettierignore

@@ -1,7 +1,6 @@
 pnpm-lock.yaml
 dist
-coverage/
 LICENSE
-components.d.ts
-src/assets/locales/*.json
-!src/assets/locales/en.json
+openapi.json
+docs/40-cli.md
+build/

docs/docs/30-administration/10-configuration/12-forges/11-overview.md

@@ -10,6 +10,6 @@
 | Event: Release                                                   |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                        :x:                         |
 | Event: Deploy¹                                                   |   :white_check_mark:   |         :x:          |           :x:            |          :x:           |             :x:              |                        :x:                         |
 | [Multiple workflows](../../../20-usage/25-workflows.md)          |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |      :white_check_mark:      |                 :white_check_mark:                 |
-| [when.path filter](../../../20-usage/20-workflow-syntax.md#path) |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                        :white_check_mark:                         |
+| [when.path filter](../../../20-usage/20-workflow-syntax.md#path) |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                 :white_check_mark:                 |
 
 ¹ The deployment event can be triggered for all forges from Woodpecker directly. However, only GitHub can trigger them using webhooks.

docs/docs/92-development/03-ui.md

@@ -15,12 +15,12 @@ After starting the Woodpecker server as explained in the [debugging](./01-gettin
 
 ### Usage with remote server
 
- If you would like to test your UI changes on a "real-world" Woodpecker server which probably has more complex data than local test instances, you can run `pnpm start` with these environment variables:
+If you would like to test your UI changes on a "real-world" Woodpecker server which probably has more complex data than local test instances, you can run `pnpm start` with these environment variables:
 
 - `VITE_DEV_PROXY`: your server URL, for example `https://ci.woodpecker-ci.org`
 - `VITE_DEV_USER_SESS_COOKIE`: the value `user_sess` cookie in your browser
 
- Then, open the UI at `http://localhost:8010`.
+Then, open the UI at `http://localhost:8010`.
 
 ## Tools and frameworks
 

docs/package.json

@@ -11,7 +11,9 @@
     "clear": "docusaurus clear",
     "serve": "docusaurus serve",
     "write-translations": "docusaurus write-translations",
-    "write-heading-ids": "docusaurus write-heading-ids"
+    "write-heading-ids": "docusaurus write-heading-ids",
+    "format": "prettier --write .",
+    "format:check": "prettier -c ."
   },
   "dependencies": {
     "@docusaurus/core": "^3.8.1",
@@ -46,6 +48,7 @@
     "@types/react": "^19.1.7",
     "@types/react-helmet": "^6.1.11",
     "@types/react-router-dom": "^5.3.3",
+    "prettier": "^3.6.2",
     "typescript": "^5.8.3"
   }
 }

docs/plugins/woodpecker-plugins/src/index.ts

@@ -4,7 +4,6 @@ import { LoadContext, Plugin, PluginContentLoadedActions } from '@docusaurus/typ
 import axios, { AxiosError } from 'axios';
 import slugify from 'slugify';
 
-
 import * as markdown from './markdown';
 import { Content, WoodpeckerPlugin, WoodpeckerPluginHeader, WoodpeckerPluginIndexEntry } from './types';
 
@@ -27,7 +26,7 @@ async function loadContent(): Promise<Content> {
             i.docs,
             axiosError.message,
             axiosError.response?.status,
-            axiosError.response?.statusText
+            axiosError.response?.statusText,
           );
           return undefined;
         }

docs/plugins/woodpecker-plugins/src/markdown.ts

@@ -19,7 +19,7 @@ export function getRawHeader(data: string): string {
 }
 
 export async function getContent(data: string): Promise<string> {
-  const marked = await import('marked')
+  const marked = await import('marked');
 
   const content = data.replace(regexContent, '').replace(/<!--(.*?)-->/gm, '');
   if (!content) {

docs/src/pages/migrations.md

@@ -116,7 +116,6 @@ The following restructuring was done to achieve a more consistent grouping:
   Additionally, the description has been updated to reflect that these filters only apply to plugins ([#4069](https://github.com/woodpecker-ci/woodpecker/pull/4069)).
 
 - SDK changes:
-
   - The SDK fields `start_time`, `end_time`, `created_at`, `started_at`, `finished_at` and `reviewed_at` have been renamed to `started`, `finished`, `created`, `started`, `finished`, `reviewed` ([#3968](https://github.com/woodpecker-ci/woodpecker/pull/3968))
   - The `trusted` field of the repo model was changed from `boolean` to `object` ([#4025](https://github.com/woodpecker-ci/woodpecker/pull/4025))
 
@@ -279,14 +278,12 @@ Read more about it in [#4213](https://github.com/woodpecker-ci/woodpecker/pull/4
 
 - Dropped support for `DRONE_*` environment variables. The according `WOODPECKER_*` variables must be used instead.
   Additionally some alternative namings have been removed to simplify maintenance:
-
   - `WOODPECKER_AGENT_SECRET` replaces `WOODPECKER_SECRET`, `DRONE_SECRET`, `WOODPECKER_PASSWORD`, `DRONE_PASSWORD` and `DRONE_AGENT_SECRET`.
   - `WOODPECKER_HOST` replaces `DRONE_HOST` and `DRONE_SERVER_HOST`.
   - `WOODPECKER_DATABASE_DRIVER` replaces `DRONE_DATABASE_DRIVER` and `DATABASE_DRIVER`.
   - `WOODPECKER_DATABASE_DATASOURCE` replaces `DRONE_DATABASE_DATASOURCE` and `DATABASE_CONFIG`.
 
 - Dropped support for `DRONE_*` environment variables in pipeline steps. Pipeline meta-data can be accessed with `CI_*` variables.
-
   - `CI_*` prefix replaces `DRONE_*`
   - `CI` value is now `woodpecker`
   - `DRONE=true` has been removed
@@ -316,7 +313,6 @@ Read more about it in [#4213](https://github.com/woodpecker-ci/woodpecker/pull/4
 - Default workspace base path has moved from `/drone` to `/woodpecker`
 
 - Default SQLite database location has changed:
-
   - `/var/lib/drone/drone.sqlite` -> `/var/lib/woodpecker/woodpecker.sqlite`
   - `drone.sqlite` -> `woodpecker.sqlite`
 

docs/versioned_docs/version-2.8/91-migrations.md

@@ -84,14 +84,12 @@ Some versions need some changes to the server configuration or the pipeline conf
 
 - Dropped support for `DRONE_*` environment variables. The according `WOODPECKER_*` variables must be used instead.
   Additionally some alternative namings have been removed to simplify maintenance:
-
   - `WOODPECKER_AGENT_SECRET` replaces `WOODPECKER_SECRET`, `DRONE_SECRET`, `WOODPECKER_PASSWORD`, `DRONE_PASSWORD` and `DRONE_AGENT_SECRET`.
   - `WOODPECKER_HOST` replaces `DRONE_HOST` and `DRONE_SERVER_HOST`.
   - `WOODPECKER_DATABASE_DRIVER` replaces `DRONE_DATABASE_DRIVER` and `DATABASE_DRIVER`.
   - `WOODPECKER_DATABASE_DATASOURCE` replaces `DRONE_DATABASE_DATASOURCE` and `DATABASE_CONFIG`.
 
 - Dropped support for `DRONE_*` environment variables in pipeline steps. Pipeline meta-data can be accessed with `CI_*` variables.
-
   - `CI_*` prefix replaces `DRONE_*`
   - `CI` value is now `woodpecker`
   - `DRONE=true` has been removed
@@ -121,7 +119,6 @@ Some versions need some changes to the server configuration or the pipeline conf
 - Default workspace base path has moved from `/drone` to `/woodpecker`
 
 - Default SQLite database location has changed:
-
   - `/var/lib/drone/drone.sqlite` -> `/var/lib/woodpecker/woodpecker.sqlite`
   - `drone.sqlite` -> `woodpecker.sqlite`
 

docs/versioned_docs/version-3.8/30-administration/10-configuration/12-forges/11-overview.md

@@ -10,6 +10,6 @@
 | Event: Release                                                   |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                        :x:                         |
 | Event: Deploy¹                                                   |   :white_check_mark:   |         :x:          |           :x:            |          :x:           |             :x:              |                        :x:                         |
 | [Multiple workflows](../../../20-usage/25-workflows.md)          |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |      :white_check_mark:      |                 :white_check_mark:                 |
-| [when.path filter](../../../20-usage/20-workflow-syntax.md#path) |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                        :white_check_mark:                         |
+| [when.path filter](../../../20-usage/20-workflow-syntax.md#path) |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                 :white_check_mark:                 |
 
 ¹ The deployment event can be triggered for all forges from Woodpecker directly. However, only GitHub can trigger them using webhooks.

docs/versioned_docs/version-3.9/30-administration/10-configuration/12-forges/11-overview.md

@@ -10,6 +10,6 @@
 | Event: Release                                                   |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                        :x:                         |
 | Event: Deploy¹                                                   |   :white_check_mark:   |         :x:          |           :x:            |          :x:           |             :x:              |                        :x:                         |
 | [Multiple workflows](../../../20-usage/25-workflows.md)          |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |      :white_check_mark:      |                 :white_check_mark:                 |
-| [when.path filter](../../../20-usage/20-workflow-syntax.md#path) |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                        :white_check_mark:                         |
+| [when.path filter](../../../20-usage/20-workflow-syntax.md#path) |   :white_check_mark:   |  :white_check_mark:  |    :white_check_mark:    |   :white_check_mark:   |             :x:              |                 :white_check_mark:                 |
 
 ¹ The deployment event can be triggered for all forges from Woodpecker directly. However, only GitHub can trigger them using webhooks.

docs/versioned_docs/version-3.9/40-cli.md

@@ -56,7 +56,6 @@ woodpecker-cli [GLOBAL OPTIONS] [command [COMMAND OPTIONS]] [ARGUMENTS...]
 
 **--token, -t**="": server auth token
 
-
 # COMMANDS
 
 ## admin
@@ -404,9 +403,9 @@ execute a local pipeline
 
 **--workflow-number**="": Set the metadata environment variable "CI_WORKFLOW_NUMBER". (default: 0)
 
-**--workspace-base**="":  (default: /woodpecker)
+**--workspace-base**="": (default: /woodpecker)
 
-**--workspace-path**="":  (default: src)
+**--workspace-path**="": (default: src)
 
 ## info
 

docs/versions.json

@@ -1,6 +1 @@
-[
-  "3.9",
-  "3.8",
-  "3.7",
-  "2.8"
-]
+["3.9", "3.8", "3.7", "2.8"]