From c195cc591ce7c2d0a2942aff57138b0af19b8076 Mon Sep 17 00:00:00 2001 From: Gusted Date: Fri, 21 Feb 2025 14:43:52 +0100 Subject: [PATCH] fix: preview script set release-schedule - Ref: https://codeberg.org/forgejo/website/commit/4d8bc434a17561fb94f888624228216cb534f292 - Add a symbolic link for the current `release-schedule.json` to the `forgejo-docs/next/release-schedule.json` location, so the forgejo website knows which releases are stable, LTS and when they are EOL. This is required to make the forgejo website run properly. --- scripts/preview.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/scripts/preview.sh b/scripts/preview.sh index 0dbd6fd6..abba0233 100755 --- a/scripts/preview.sh +++ b/scripts/preview.sh @@ -37,6 +37,9 @@ rm -rf ./public/images/$current_branch mkdir -p $(dirname ./src/content/images/$current_branch) # in case of branch names with slashes ln -s $repo_path/images/ ./public/images/$current_branch +rm -rf ./forgejo-docs/next/release-schedule.json +ln -s $repo_path/release-schedule.json ./forgejo-docs/next/release-schedule.json + # once the dev server is running, open the current docs branch in the browser sleep 3 && $open_cmd http://localhost:4321/docs/$current_branch/ &