in the case of a release that is not yet published, it will exist as
release candidates in the experimental organization. Every release go
through there and it is a reliable source.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/542
Reviewed-by: crystal <crystal@noreply.codeberg.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
(cherry picked from commit 4ce64e2840)
They get /forgejo/forgejo/archive/100448a007707c049a769cb71cd170fcb5b64a25.bundle
despite https://code.forgejo.org/robots.txt having
Disallow: /*/*/archive/
Disallow: /*/*/archive/*.bundle
Hi,
somehow I made a hash of the last PR #522 so it failed linting again. I hope it is ok now. Sorry for the noise!
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/525
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Christian Drexler <xunzi@noreply.codeberg.org>
Co-committed-by: Christian Drexler <xunzi@noreply.codeberg.org>
This reverts commit 28cdb8ca82, because
the functionality has been superseded by a different implementation.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
It was quite painful yesterday to try to figure out why my workflow didn't work anymore after the Forgejo migration. Turns out that `gitea/act_runner` used a different default Docker image. With this PR, it should be clearer to other people what is the meaning of the labels.
Co-authored-by: Rik Huijzer <github@huijzer.xyz>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/475
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Rik Huijzer <rikh@noreply.codeberg.org>
Co-committed-by: Rik Huijzer <rikh@noreply.codeberg.org>
This PR extends the examples that were provided by @earl-warren in https://codeberg.org/forgejo/runner. I've tested this configuration twice today on two completely separate servers. For more information about the whole process that I've used, see https://huijzer.xyz/posts/forgejo-setup/.
I'll try to extract upstream a bit more information to the Forgejo docs. Feel free to take anything from my blog that seems useful and don't worry about credits. Feel free to copy whatever seems useful.
Co-authored-by: Rik Huijzer <github@huijzer.xyz>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/474
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Rik Huijzer <rikh@noreply.codeberg.org>
Co-committed-by: Rik Huijzer <rikh@noreply.codeberg.org>
It doesn't feel right to have such guide on the installation page, it
feels more natural to have it's own page. This also keeps the
'installation' page clean, which currently feels more like an index
page, given it's linking to two other pages (installation from {binary,docker}).
