README: explain why setup-forgejo is needed for local debug
This commit is contained in:
parent
74d11b5eaf
commit
985388b5b6
1 changed files with 8 additions and 0 deletions
|
@ -24,6 +24,14 @@ as:
|
||||||
|
|
||||||
Use setup-forgejo from source.
|
Use setup-forgejo from source.
|
||||||
|
|
||||||
|
The [setup-forgejo](https://code.forgejo.org/actions/setup-forgejo)
|
||||||
|
repository is a [Forgejo
|
||||||
|
Action](https://forgejo.org/docs/v1.21/user/actions/) which is meant
|
||||||
|
to be used in workflows. However, it is implemented as shell scripts that
|
||||||
|
can also be used to create Forgejo instances and runners locally. This
|
||||||
|
is convenient for testing and the reason why it needs to be added to the PATH.
|
||||||
|
For instance, it is a dependency of the `actions/run.sh` script.
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
git clone https://code.forgejo.org/actions/setup-forgejo
|
git clone https://code.forgejo.org/actions/setup-forgejo
|
||||||
export PATH=$(pwd)/setup-forgejo:$PATH
|
export PATH=$(pwd)/setup-forgejo:$PATH
|
||||||
|
|
Loading…
Add table
Reference in a new issue