This PR
- adds more details regarding the nature of the secret used when registering runners offline using `forgejo-cli actions register`,
- explains how to change the secret for an existing runner ([Forgejo PR #4619](https://codeberg.org/forgejo/forgejo/pulls/4619)),
- explains how to keep the Forgejo-side command idempotent if the labels aren't known ([Forgejo PR #4610](https://codeberg.org/forgejo/forgejo/pulls/4610))
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/769
Reviewed-by: twenty-panda <twenty-panda@noreply.codeberg.org>
Co-authored-by: Emmanuel BENOÎT <tseeker@nocternity.net>
Co-committed-by: Emmanuel BENOÎT <tseeker@nocternity.net>
There is no need to duplicate the information here, it is all in
detail in the checklist and changes from release to release. Just keep
the sections that provide general background information that helps
understand the meaning of the steps of the checklist.
The USER_UID/USER_GID are not interpretd in the rootless image, use
`user: "1024:100"` in the docker-compose example instead.
Fixes: https://codeberg.org/forgejo/docs/issues/704
* do not include patch releases in the release schedule
* fix the Gitea compatibility of 7.0 & 8.0
* change the feature freeze from two to three weeks. See
* https://codeberg.org/forgejo/discussions/issues/180
* https://codeberg.org/forgejo/discussions/issues/187
* remove cutting a release in favor of copy/pasting previous
checklists
* remove release notes as it is not done on a rolling basis
* move the runner publication down as it was in the middle
of the release process sections
* reminder of LTS toolchain upgrades
This PR changes the screenshots in the Blocking users page. It not only updates the block user dialog shown in the page (since it has been [changed](/forgejo/forgejo/pulls/4204) to have better wording and explanation), but it also changes the other screenshots to be consistent with the rest of the page, oh and they used (old?) Gitea theme, not Forgejo)
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/741
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Ikuyo Kita <kitakita@disroot.org>
Co-committed-by: Ikuyo Kita <kitakita@disroot.org>
it helps to minimize the need for configuration if the default port is
used instead of a custom one.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/737
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
- Eliminated confusing topic switch https->proxy->https.
- Moved all HTTPS mentions to end of intro.
- Added paragraph about when you'd want a reverse proxy.
- Use /code for subpath, to encourage purpose-based naming
Updates the screenshot in the issue tracking basics page, as it looks very dated (even shows the old Codeberg logo)
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/716
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Ikuyo Kita <kitakita@disroot.org>
Co-committed-by: Ikuyo Kita <kitakita@disroot.org>
