Codeberg Pages: note the public-repository requirement

The `pages` repository must be public for git-pages to serve it, but this
was only stated on the "pushing output" page. Newcomers following the
quickstart or hitting an unpublished site had no signal.

Add a warning admonition to the Pages getting-started page and a
troubleshooting entry covering the "my site won't publish" case.

Closes #748

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
swiftdoc 2026-05-29 15:45:20 -04:00
parent e0fe2eaa66
commit e35d1a3c3d
2 changed files with 14 additions and 0 deletions

View file

@ -45,6 +45,14 @@ There are two ways to get started with Codeberg Pages on git-pages:
This page documents the first method. See the [separate page on using Forgejo Actions](/codeberg-pages/forgejo-actions/) for information on the second method.
{% admonition "warning" %}
The `pages` repository **must** be public, as Codeberg Pages directly fetches the files from the repository,
just like an ordinary visitor would.
A private repository will not be served.
{% endadmonition %}
### User/organization websites
1. Create a repository called `pages` under your own username or under the organization you want to create a website for

View file

@ -14,6 +14,12 @@ contains a sub-sub-domain which does not work with Let's Encrypt wildcard certif
Use the alternative URL <https://pages.codeberg.org/user.name/> as a workaround or rename you repository
(e.g. replace `.` by `_`).
## My website is not published
Make sure the `pages` repository is **public**.
Codeberg Pages directly fetches the files from the repository, just like an ordinary visitor would,
so a private repository will not be served.
## My content is not updated
The Codeberg Pages v2 server caches files under a certain size (currently 1 MiB).