Skip to content

Commit 6e48107

Browse files
committed
docs/make-release.md: Corrected slash in release branch notes
1 parent d8041a7 commit 6e48107

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/make-release.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -409,7 +409,7 @@ Next, follow the same procedure starting at [Tag the HEAD Commit](#tag-the-head-
409409
Finally, merge the release branch back into the main branch and push the changes to the upstream repository.
410410

411411
> [!IMPORTANT]
412-
> Release branches start with `release\v`.
412+
> Release branches start with `release/v`.
413413
414414
```console
415415
git checkout main
@@ -422,7 +422,7 @@ git push <remote-name> main
422422
From this point, the release will be tracked historically using the Git tag, so there is no reason to keep the release branch once it has been merged. You may wish to delay the deletion for a few days in case it is needed for some reason, but when you are ready, the commands to delete the local and remote branches are:
423423

424424
> [!IMPORTANT]
425-
> Release branches start with `release\v`. Take care not to delete the tag, which starts with a `v`.
425+
> Release branches start with `release/v`. Take care not to delete the tag, which starts with a `v`.
426426
427427
```console
428428
git branch -d <release-branch>

0 commit comments

Comments
 (0)