mirror of
https://codeberg.org/Codeberg/Documentation.git
synced 2026-08-15 14:53:29 -07:00
chore(ci): Try fixing CI
This commit is contained in:
parent
38dd33db6c
commit
1d4591b8b4
3 changed files with 6 additions and 5 deletions
|
|
@ -125,7 +125,8 @@
|
|||
"Merch",
|
||||
"merch",
|
||||
"freewear",
|
||||
"gedankenstuecke"
|
||||
"gedankenstuecke",
|
||||
"Zstd"
|
||||
],
|
||||
"ignorePaths": [
|
||||
"**/node_modules/**/*",
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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 don’t know that for sure.
|
||||
Need to check.
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ git-pages-cli --debug-manifest https://example.org
|
|||
In either case, you get huge JSONs with meta-information about the website.
|
||||
The structure is roughly:
|
||||
|
||||
``` json
|
||||
```json
|
||||
{
|
||||
"repoUrl": "https://codeberg.org/.../pages.git",
|
||||
"branch": "pages",
|
||||
|
|
@ -105,7 +105,7 @@ The structure is roughly:
|
|||
"to": "/bar",
|
||||
"status": 301,
|
||||
"force": false
|
||||
},
|
||||
}
|
||||
// ...
|
||||
],
|
||||
"headers": [],
|
||||
|
|
|
|||
Loading…
Reference in a new issue