From da549f6a239230c384b151c9a90153c17552656d Mon Sep 17 00:00:00 2001 From: mike Date: Fri, 24 Sep 2021 15:57:18 +0200 Subject: [PATCH] Fixes a single internal link to the Tag article (#169) Co-authored-by: Michiel Appelman Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/169 Co-authored-by: mike Co-committed-by: mike --- content/collaborating/citable-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/collaborating/citable-code.md b/content/collaborating/citable-code.md index acec898..d5b11a6 100644 --- a/content/collaborating/citable-code.md +++ b/content/collaborating/citable-code.md @@ -14,7 +14,7 @@ This page will show you how to do just that. The process can be decomposed in fo ## Create a release of your repository Creating a release is optional but recommended. The reason is simply that a release will make it explicit what version of your code you want to share/cite. Any further edits to your code will not be included in the release. In other words, it is good practice to share/cite a release with fixed code rather than the always changing code of your repository. -You can find instructions on the [Tags and Releases article](git/using-tags/#creating-tags-and-releases). +You can find instructions on the [Tags and Releases article](/git/using-tags/#creating-tags-and-releases). ## Download the ZIP archive If you did create a release, download the ZIP archive of the source code on the `Releases` tab of your repository, as shown in the previous screenshot.