From 83e6c15b0ea252d5475c3a5af25279765e19aa4d Mon Sep 17 00:00:00 2001 From: Angel Pons Date: Fri, 20 Nov 2020 16:30:24 +0100 Subject: Doc/releases/checklist.md: Clarify tag push command Change-Id: I0a6d1ed014c6454c4bde390283351c19fe097201 Signed-off-by: Angel Pons Reviewed-on: https://review.coreboot.org/c/coreboot/+/47813 Reviewed-by: Paul Menzel Reviewed-by: Patrick Georgi Tested-by: build bot (Jenkins) --- Documentation/releases/checklist.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'Documentation') diff --git a/Documentation/releases/checklist.md b/Documentation/releases/checklist.md index d777f0e38b..3f19bfb6da 100644 --- a/Documentation/releases/checklist.md +++ b/Documentation/releases/checklist.md @@ -177,8 +177,9 @@ commit db508565d2483394b709654c57533e55eebace51 (HEAD, tag: 4.6, origin/master, ... ```` -When you used the script to generate the release, a tag was generated in the tree that was downloaded. -From the coreboot-X.Y tree, just run: `git push -f origin ` +When you used the script to generate the release, a signed tag was generated in the +tree that was downloaded. From the coreboot-X.Y tree, just run: `git push origin X.Y`. +In case you pushed the wrong tag already, you have to force push the new one. You will need write access for tags to the coreboot git repo to do this. -- cgit v1.2.3