From 59ef598b49ec8002972ce4d0640a340090994c04 Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Tue, 28 Jan 2025 16:33:32 +0000 Subject: [PATCH] fix admin url for 1.23.0 (#164) I am running the release candidate and found the admin URL changed. https://github.com/go-gitea/gitea/pull/32189 Reviewed-on: https://gitea.com/gitea/docs/pulls/164 Reviewed-by: techknowlogick Co-authored-by: Brandon Philips Co-committed-by: Brandon Philips --- docs/help/faq.md | 4 ++-- docs/usage/actions/act-runner.md | 2 +- docs/usage/actions/quickstart.md | 2 +- runner/index.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/help/faq.md b/docs/help/faq.md index c763fe9b..d0718218 100644 --- a/docs/help/faq.md +++ b/docs/help/faq.md @@ -330,9 +330,9 @@ It is highly recommended to back-up your database before running these commands. - Add your (bare) repositories to the correct spot for your configuration (`repository.ROOT`), ensuring they are in the correct layout `/[user]/[repo].git`. - **Note:** the directory names must be lowercase. - - You can also check `/admin/config` for the repository root path. + - You can also check `/-/admin/config` for the repository root path. - Ensure that the user/org exists that you want to adopt repositories for. -- As an admin, go to `/admin/repos/unadopted` and search. +- As an admin, go to `/-/admin/repos/unadopted` and search. - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository). - If the above steps are done correctly, you should be able to select repositories to adopt. - If no repositories are found, enable [debug logging](../administration/config-cheat-sheet.md#repository-repository) to check for any specific errors. diff --git a/docs/usage/actions/act-runner.md b/docs/usage/actions/act-runner.md index 91fc7df9..31037b72 100644 --- a/docs/usage/actions/act-runner.md +++ b/docs/usage/actions/act-runner.md @@ -48,7 +48,7 @@ Note that the repository may still use instance-level or organization-level runn Before register the runner and run it, you need a registration token. The level of the runner determines where to obtain the registration token. -- Instance level: The admin settings page, like `/admin/actions/runners`. +- Instance level: The admin settings page, like `/-/admin/actions/runners`. - Organization level: The organization settings page, like `//settings/actions/runners`. - Repository level: The repository settings page, like `///settings/actions/runners`. diff --git a/docs/usage/actions/quickstart.md b/docs/usage/actions/quickstart.md index c9e2297d..13abd223 100644 --- a/docs/usage/actions/quickstart.md +++ b/docs/usage/actions/quickstart.md @@ -55,7 +55,7 @@ If you are unsure which address to use, the LAN address is usually the right cho Each token can be used to create multiple runners, until it is replaced with a new token using the reset link. You can obtain different levels of 'tokens' from the following places to create the corresponding level of 'runners': -- Instance level: The admin settings page, like `/admin/actions/runners`. +- Instance level: The admin settings page, like `/-/admin/actions/runners`. - Organization level: The organization settings page, like `//settings/actions/runners`. - Repository level: The repository settings page, like `///settings/actions/runners`. diff --git a/runner/index.md b/runner/index.md index 6c47ed9c..e9e64b52 100644 --- a/runner/index.md +++ b/runner/index.md @@ -39,7 +39,7 @@ And you will be asked to input: 1. Gitea instance URL, like `http://192.168.8.8:3000/`. You should use your gitea instance ROOT_URL as the instance argument and you should not use `localhost` or `127.0.0.1` as instance IP; -2. Runner token, you can get it from `http://192.168.8.8:3000/admin/actions/runners`; +2. Runner token, you can get it from `http://192.168.8.8:3000/-/admin/actions/runners`; 3. Runner name, you can just leave it blank; 4. Runner labels, you can just leave it blank.