From 0428d01d6f540025ef0452861f4521123146b4ca Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Tue, 25 Feb 2025 06:34:28 +0100 Subject: [PATCH] Fix typo on forgejo/gitea documentation (#4898) Co-authored-by: Luciano Hanyon Wu --- docs/docs/30-administration/11-forges/30-gitea.md | 2 +- docs/docs/30-administration/11-forges/35-forgejo.md | 2 +- .../version-3.0/30-administration/11-forges/30-gitea.md | 2 +- .../version-3.0/30-administration/11-forges/35-forgejo.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docs/30-administration/11-forges/30-gitea.md b/docs/docs/30-administration/11-forges/30-gitea.md index 82d77a54a..7c2930d45 100644 --- a/docs/docs/30-administration/11-forges/30-gitea.md +++ b/docs/docs/30-administration/11-forges/30-gitea.md @@ -33,7 +33,7 @@ To configure the Docker network if the network's name is `gitea`, configure it l ## Registration -Register your application with Gitea to create your client id and secret. You can find the OAuth applications settings of Gitea at `https://gitea./user/settings/`. It is very import the authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. +Register your application with Gitea to create your client id and secret. You can find the OAuth applications settings of Gitea at `https://gitea./user/settings/`. It is very important that authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. If you run the Woodpecker CI server on the same host as the Gitea instance, you might also need to allow local connections in Gitea, since version `v1.16`. Otherwise webhooks will fail. Add the following lines to your Gitea configuration (usually at `/etc/gitea/conf/app.ini`). diff --git a/docs/docs/30-administration/11-forges/35-forgejo.md b/docs/docs/30-administration/11-forges/35-forgejo.md index 5b89d8051..568c121c6 100644 --- a/docs/docs/30-administration/11-forges/35-forgejo.md +++ b/docs/docs/30-administration/11-forges/35-forgejo.md @@ -33,7 +33,7 @@ To configure the Docker network if the network's name is `forgejo`, configure it ## Registration -Register your application with Forgejo to create your client id and secret. You can find the OAuth applications settings of Forgejo at `https://forgejo./user/settings/`. It is very import the authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. +Register your application with Forgejo to create your client id and secret. You can find the OAuth applications settings of Forgejo at `https://forgejo./user/settings/`. It is very important that authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. If you run the Woodpecker CI server on the same host as the Forgejo instance, you might also need to allow local connections in Forgejo. Otherwise webhooks will fail. Add the following lines to your Forgejo configuration (usually at `/etc/forgejo/conf/app.ini`). diff --git a/docs/versioned_docs/version-3.0/30-administration/11-forges/30-gitea.md b/docs/versioned_docs/version-3.0/30-administration/11-forges/30-gitea.md index 82d77a54a..7c2930d45 100644 --- a/docs/versioned_docs/version-3.0/30-administration/11-forges/30-gitea.md +++ b/docs/versioned_docs/version-3.0/30-administration/11-forges/30-gitea.md @@ -33,7 +33,7 @@ To configure the Docker network if the network's name is `gitea`, configure it l ## Registration -Register your application with Gitea to create your client id and secret. You can find the OAuth applications settings of Gitea at `https://gitea./user/settings/`. It is very import the authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. +Register your application with Gitea to create your client id and secret. You can find the OAuth applications settings of Gitea at `https://gitea./user/settings/`. It is very important that authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. If you run the Woodpecker CI server on the same host as the Gitea instance, you might also need to allow local connections in Gitea, since version `v1.16`. Otherwise webhooks will fail. Add the following lines to your Gitea configuration (usually at `/etc/gitea/conf/app.ini`). diff --git a/docs/versioned_docs/version-3.0/30-administration/11-forges/35-forgejo.md b/docs/versioned_docs/version-3.0/30-administration/11-forges/35-forgejo.md index 5b89d8051..1438e1556 100644 --- a/docs/versioned_docs/version-3.0/30-administration/11-forges/35-forgejo.md +++ b/docs/versioned_docs/version-3.0/30-administration/11-forges/35-forgejo.md @@ -33,7 +33,7 @@ To configure the Docker network if the network's name is `forgejo`, configure it ## Registration -Register your application with Forgejo to create your client id and secret. You can find the OAuth applications settings of Forgejo at `https://forgejo./user/settings/`. It is very import the authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. +Register your application with Forgejo to create your client id and secret. You can find the OAuth applications settings of Forgejo at `https://forgejo./user/settings/`. It is very important that the authorization callback URL matches your http(s) scheme and hostname exactly with `https:///authorize` as the path. If you run the Woodpecker CI server on the same host as the Forgejo instance, you might also need to allow local connections in Forgejo. Otherwise webhooks will fail. Add the following lines to your Forgejo configuration (usually at `/etc/forgejo/conf/app.ini`).