From 83647822225a2f91830f5da4729af0140a2ade81 Mon Sep 17 00:00:00 2001 From: Eric Engestrom Date: Sun, 23 Feb 2025 00:31:55 +0100 Subject: [PATCH] docs: update gitlab docs urls GitLab finally dropped the split between "docs for paid users" and "docs for free users", and in the process re-shuffled some things. Part-of: --- .gitlab/issue_templates/Bug Report - AMD Radeon Vulkan.md | 4 ++-- .gitlab/issue_templates/Bug Report.md | 4 ++-- CODEOWNERS | 2 +- bin/ci/gitlab_common.py | 2 +- docs/ci/index.rst | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/.gitlab/issue_templates/Bug Report - AMD Radeon Vulkan.md b/.gitlab/issue_templates/Bug Report - AMD Radeon Vulkan.md index 6cc69a4fac1..eb938c85868 100644 --- a/.gitlab/issue_templates/Bug Report - AMD Radeon Vulkan.md +++ b/.gitlab/issue_templates/Bug Report - AMD Radeon Vulkan.md @@ -2,7 +2,7 @@ - Check if a new version of Mesa is available which might have fixed the problem. - If you can, check if the latest development version (git main) works better. - Check if your bug has already been reported here. -- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks), GitLab removes line breaks without this. +- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/user/markdown/#code-spans-and-blocks), GitLab removes line breaks without this. - Do not paste long logs directly into the description. Use https://gitlab.freedesktop.org/-/snippets/new, attachments, or a pastebin with a long expiration instead. - As examples of good bug reports you may review one of these - #2598, #2615, #2608 @@ -44,7 +44,7 @@ Example: ### System information -Please post `inxi -GSC -xx` output ([fenced with triple backticks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks)) OR fill information below manually +Please post `inxi -GSC -xx` output ([fenced with triple backticks](https://docs.gitlab.com/user/markdown/#code-spans-and-blocks)) OR fill information below manually - OS: (`cat /etc/os-release | grep "NAME"`) diff --git a/.gitlab/issue_templates/Bug Report.md b/.gitlab/issue_templates/Bug Report.md index 474bd89772e..f4e5824b815 100644 --- a/.gitlab/issue_templates/Bug Report.md +++ b/.gitlab/issue_templates/Bug Report.md @@ -2,7 +2,7 @@ - Check if a new version of Mesa is available which might have fixed the problem. - If you can, check if the latest development version (git main) works better. - Check if your bug has already been reported here. -- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks), GitLab removes line breaks without this. +- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/user/markdown/#code-spans-and-blocks), GitLab removes line breaks without this. - Do not paste long logs directly into the description. Use https://gitlab.freedesktop.org/-/snippets/new, attachments, or a pastebin with a long expiration instead. - As examples of good bug reports you may review one of these - #2598, #2615, #2608 @@ -16,7 +16,7 @@ The title should effectively distinguish this bug report from others and be spec ### System information -Please post `inxi -GSC -xx` output ([fenced with triple backticks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks)) OR fill information below manually +Please post `inxi -GSC -xx` output ([fenced with triple backticks](https://docs.gitlab.com/user/markdown/#code-spans-and-blocks)) OR fill information below manually - OS: (`cat /etc/os-release | grep "NAME"`) diff --git a/CODEOWNERS b/CODEOWNERS index e69639d3211..405849db92d 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -1,6 +1,6 @@ # This file contains the GitLab handle of the maintainers/reviewers for # a given file: -# https://docs.gitlab.com/ce/user/project/code_owners.html +# https://docs.gitlab.com/user/project/codeowners/ # # Consider these as the list of people who want to be involved in MRs # touching these files/folders, and whom you can ask your questions and diff --git a/bin/ci/gitlab_common.py b/bin/ci/gitlab_common.py index 46b43a0a70c..9f5cfd81656 100644 --- a/bin/ci/gitlab_common.py +++ b/bin/ci/gitlab_common.py @@ -18,7 +18,7 @@ from pathlib import Path GITLAB_URL = "https://gitlab.freedesktop.org" TOKEN_DIR = Path(os.getenv("XDG_CONFIG_HOME") or Path.home() / ".config") -# Known GitLab token prefixes: https://docs.gitlab.com/ee/security/token_overview.html#token-prefixes +# Known GitLab token prefixes: https://docs.gitlab.com/security/tokens/#token-prefixes TOKEN_PREFIXES: dict[str, str] = { "Personal access token": "glpat-", "OAuth Application Secret": "gloas-", diff --git a/docs/ci/index.rst b/docs/ci/index.rst index 484672b00dd..b9bd9b31f2e 100644 --- a/docs/ci/index.rst +++ b/docs/ci/index.rst @@ -215,7 +215,7 @@ faster personal machine as a runner. You can find the gitlab-runner package in Debian, or use GitLab's own builds. To do so, follow `GitLab's instructions -`__ +`__ to register your personal GitLab runner in your Mesa fork. Then, tell Mesa how many jobs it should serve (``concurrent=``) and how many cores those jobs should use (``FDO_CI_CONCURRENT=``) by editing these