pages: Slightly rewrite the splat restrictions in migration post

Co-Authored-by: @whitequark
This commit is contained in:
Artyom Bologov 2026-07-22 12:57:10 +04:00
parent c889194235
commit bfc8c6eda5

View file

@ -34,7 +34,7 @@ Please be aware of the following changes and deprecated features.
- `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.
- Splat redirects only work for simple `/path/to/splat/*/ /new/path/to/:splat` patterns of moved posts, no way to e.g. replace file extension with `/*/ /:splat.html`.
- 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