From 885ed9491a532ec02094dba7ad7d3a45ce076f7d Mon Sep 17 00:00:00 2001 From: Morten Piibeleht Date: Mon, 14 Aug 2023 18:51:02 +1200 Subject: [PATCH] docs: fix GitHub link 301 (#2209) --- docs/src/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/contributing.md b/docs/src/contributing.md index 2ce85afa6b..ec85b049ea 100644 --- 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.