From 4026c827be352f39fa34721525d1d7bbf4238c77 Mon Sep 17 00:00:00 2001 From: bjoern Date: Mon, 25 Nov 2024 17:34:20 +0100 Subject: [PATCH] prefer long options in RELEASE.md (#6136) using long options make things less mystical, it is clearer what happens. (apart from that i also disallowed `git -a` on my machine in general, as `git commit -a` is considered harmful. as my approach to disallow that is a bit greedy and disallows `-a` just for any git commands, this is the only place where i regularly struggle :) --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index d206bdfc61..f150716cb8 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -14,8 +14,8 @@ For example, to release version 1.116.0 of the core, do the following steps. 5. Commit the changes as `chore(release): prepare for 1.116.0`. Optionally, use a separate branch like `prep-1.116.0` for this commit and open a PR for review. -6. Tag the release: `git tag -a v1.116.0`. +6. Tag the release: `git tag --annotate v1.116.0`. 7. Push the release tag: `git push origin v1.116.0`. -8. Create a GitHub release: `gh release create v1.116.0 -n ''`. +8. Create a GitHub release: `gh release create v1.116.0 --notes ''`.