Try fixing CI (#857)

This is an attempt to try fixing CI errors, as seen in 38dd33d Woodpecker run. Might not be complete, but the only thing missing is Apple Authenticator link fix, which is flaky.

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/857
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
This commit is contained in:
Artyom Bologov 2026-07-25 21:17:20 +02:00 committed by Robert Wolff
parent 38dd33db6c
commit 6a78a4c7d8
3 changed files with 6 additions and 5 deletions

View file

@ -125,7 +125,8 @@
"Merch",
"merch",
"freewear",
"gedankenstuecke"
"gedankenstuecke",
"Zstd"
],
"ignorePaths": [
"**/node_modules/**/*",

View file

@ -33,7 +33,7 @@ Please be aware of the following changes and deprecated features.
- Content is no longer fetched automatically. You need to use a method that informs git-pages about changes.
- `raw.codeberg.page` is no longer available. CORS headers are now directly set on your page and this workaround is no longer necessary.
- Direct access to repos and branches is no longer possible. You can no longer use the `/repository/@branch` access. `git-pages` restricts you to the website you explicitly deployed. Serving arbitrary resources from Codeberg was a common abuse vector and is going to be deprecated.
- There no longer are automatic redirections from `path` to `path.html`, add a [redirect rule](/codeberg-pages/advanced-usage/#redirects) for each of the pages you need to redirect.
- There no longer are automatic redirects from `path` to `path.html`, add a [redirect rule](/codeberg-pages/advanced-usage/#redirects) for each of the pages you need to redirect.
- Splat redirects only work for simple `/old-path/* /new-path/:splat` patterns of moved posts, no way to e.g. replace file extension with `/* /:splat.html`.
## The first push

View file

@ -42,7 +42,7 @@ Say, we add this (broken) [redirect rule](/codeberg-pages/advanced-usage/#redire
```
After committing it and opening a page like `https://example.org/hello`, we are redirected to a 404 page.
Something must be brokein in redirects.
Something must be broken in redirects.
However, we dont know that for sure.
Need to check.
@ -105,7 +105,7 @@ The structure is roughly:
"to": "/bar",
"status": 301,
"force": false
},
}
// ...
],
"headers": [],