mirror of
https://codeberg.org/Codeberg/Documentation.git
synced 2026-06-16 05:13:54 -07:00
fix: reference latest docs for Forgejo Runner & Actions, not next
This commit is contained in:
parent
f717140c07
commit
3b05c0d3e9
2 changed files with 2 additions and 2 deletions
|
|
@ -49,7 +49,7 @@ determine where your Runner will accept workflows from.
|
|||
|
||||
## Installing Forgejo Runner
|
||||
|
||||
For the installation of the runner, see the [Forgejo documentation](https://forgejo.org/docs/next/admin/actions/runner-installation/).
|
||||
For the installation of the runner, see the [Forgejo documentation](https://forgejo.org/docs/latest/admin/actions/runner-installation/).
|
||||
|
||||
## References
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ The `token` will automatically be filled by Forgejo Actions with a secret token,
|
|||
|
||||
If you use branches to test out new features, write draft blog posts, etc., you should either limit the whole workflow, or this step only, to pushes to a default branch (usually `main` or `master`) to ensure that only finalized content is published to your site.
|
||||
|
||||
To do this, either add a [`on.push.branches` list](https://forgejo.org/docs/next/user/actions/reference/#onpush) to the whole workflow, or add [an `if` condition to the step](https://forgejo.org/docs/next/user/actions/reference/#jobsjob_idstepsif-1) (or [to the whole job](https://forgejo.org/docs/next/user/actions/reference/#jobsjob_idif)) like this:
|
||||
To do this, either add a [`on.push.branches` list](https://forgejo.org/docs/latest/user/actions/reference/#onpush) to the whole workflow, or add [an `if` condition to the step](https://forgejo.org/docs/latest/user/actions/reference/#jobsjob_idstepsif-1) (or [to the whole job](https://forgejo.org/docs/latest/user/actions/reference/#jobsjob_idif)) like this:
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue