From 0ee79afcffce4cce7b944e47a785f69c29d13795 Mon Sep 17 00:00:00 2001 From: Satvik Mishra Date: Sat, 19 Sep 2026 11:56:51 +0000 Subject: [PATCH] fix: correct Release workflow recipes link Relative ../recipes from /foundation/workflow-configuration/ resolved to /foundation/recipes/ (404). Use an absolute /recipes/release-workflow/ path and drop the redundant hash. Fixes #60 --- src/content/docs/foundation/workflow-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/foundation/workflow-configuration.md b/src/content/docs/foundation/workflow-configuration.md index cb79abe..c06a979 100644 --- a/src/content/docs/foundation/workflow-configuration.md +++ b/src/content/docs/foundation/workflow-configuration.md @@ -10,7 +10,7 @@ description: "Configure release branches, channels, and rules that control the s - Maintaining multiple lines of releases in parallel - Working on large future releases outside the normal flow of one version increment per Git push -See [Release workflow recipes](../recipes/release-workflow/#release-workflow) for detailed examples. +See [Release workflow recipes](/recipes/release-workflow/) for detailed examples. The release workflow is configured via the [branches option](/usage/configuration/#branches), which accepts either a single branch definition or an array of branch definitions. Each branch can be defined as a string, a [glob](https://github.com/micromatch/micromatch#matching-features), or an object. For string and glob definitions, defaults are applied to each [property](#branch-properties).