From 3d26dfa42d6347e6c63af18ae31ab71f4895c3e4 Mon Sep 17 00:00:00 2001 From: Lunny Xiao Date: Thu, 6 Jun 2024 22:05:38 +0800 Subject: [PATCH] Fix broken links --- docs/usage/actions/faq.md | 2 +- docusaurus.config.js | 4 ++-- versioned_docs/version-1.22/usage/actions/faq.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/usage/actions/faq.md b/docs/usage/actions/faq.md index 427d57c4..74eb0654 100644 --- a/docs/usage/actions/faq.md +++ b/docs/usage/actions/faq.md @@ -68,7 +68,7 @@ See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-act Runners have no more permissions than simply connecting to your Gitea instance. When any runner receives a job to run, it will temporarily gain limited permission to the repository associated with the job. -If you want to give more permissions to the runner, allowing it to access more private repositories or external systems, you can pass [secrets](usage/secrets.md) to it. +If you want to give more permissions to the runner, allowing it to access more private repositories or external systems, you can pass [secrets](usage/actions/secrets.md) to it. Refined permission control to Actions is a complicated job. In the future, we will add more options to Gitea to make it more configurable, such as allowing more write access to repositories or read access to all repositories in the same organization. diff --git a/docusaurus.config.js b/docusaurus.config.js index a6a2ea6c..8f9526f2 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -67,8 +67,8 @@ const config = { tagline: 'Git with a cup of tea', url: 'https://docs.gitea.com', baseUrl: '/', - onBrokenLinks: 'warn', - onBrokenMarkdownLinks: 'warn', + onBrokenLinks: 'throw', + onBrokenMarkdownLinks: 'throw', favicon: 'img/favicon.png', plugins: [ diff --git a/versioned_docs/version-1.22/usage/actions/faq.md b/versioned_docs/version-1.22/usage/actions/faq.md index 427d57c4..74eb0654 100644 --- a/versioned_docs/version-1.22/usage/actions/faq.md +++ b/versioned_docs/version-1.22/usage/actions/faq.md @@ -68,7 +68,7 @@ See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-act Runners have no more permissions than simply connecting to your Gitea instance. When any runner receives a job to run, it will temporarily gain limited permission to the repository associated with the job. -If you want to give more permissions to the runner, allowing it to access more private repositories or external systems, you can pass [secrets](usage/secrets.md) to it. +If you want to give more permissions to the runner, allowing it to access more private repositories or external systems, you can pass [secrets](usage/actions/secrets.md) to it. Refined permission control to Actions is a complicated job. In the future, we will add more options to Gitea to make it more configurable, such as allowing more write access to repositories or read access to all repositories in the same organization.