docs: fix GitHub link 301 (#2209)

JuliaDocs · Aug 14, 2023 · 885ed94 · 885ed94
1 parent c0cfded
commit 885ed94
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/src/contributing.md b/docs/src/contributing.md
@@ -17,7 +17,7 @@ Feel free to nominate commits that should be backported by opening an issue. Req
 
 ### `release-*` branches
 
-  * Each new minor version `x.y.0` gets a branch called `release-x.y` (a [protected branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)).
+  * Each new minor version `x.y.0` gets a branch called `release-x.y` (a [protected branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches)).
   * New versions are usually tagged only from the `release-x.y` branches.
   * For patch releases, changes get backported to the `release-x.y` branch via a single PR with the standard name "Backports for x.y.z" and label ["Type: Backport"](https://github.com/JuliaDocs/Documenter.jl/pulls?q=label%3A%22Type%3A+Backport%22). The PR message links to all the PRs that are providing commits to the backport. The PR gets merged as a merge commit (i.e. not squashed).
   * The old `release-*` branches may be removed once they have outlived their usefulness.