mutluyuz/Documentation:push-tags into main Add a note that tags need to be pushed to the remote target.
Please let me know, if you have any suggestions to improve the wording and this paragraph.
Add a note that tags need to be pushed to the remote target. Signed-off-by: mutluyuz <mutluyuz@noreply.codeberg.org>
@ -28,1 +28,4 @@
Please note that tags are not automatically pushed using `git push` (comparable to branches). Thus, they have to be pushed to the remote target:
```bash
git push <remote target, probably "origin"> <version number here, e.g., "v1.2.3">
Maybe we could offer the user to use the --tags argument? No need to specify the specific tag.
Thanks for the suggestions! I used the tag name because otherwise every tag is pushed what might be undesired. I added a note to the docs and mentioned both ways. What do you think about that?
lgtm.
@ -26,6 +26,16 @@ To create a tag using git, use the following command in your repo folder.
git tag -a <version number here> -m "<my tag name>"
```
Tags are not automatically pushed using `git push` (comparable to branches). Thus, they have to be pushed manually to the reemote target:
There is a typo here:
reemote -> remote
Thanks!
@ -29,0 +33,4 @@
The argument `--tags` pushes all local tags to the remote target. If you want to push only a specific tag, use:
```bash
git push <remote target, probably "origin"> <version number here, e.g., "v1.2.3">
Why do you name it "version number"? Wouldn't tag name be better suited here?
git push <remote target, probably "origin"> <specific tag name, e.g., "v1.2.3">
I agree with you. I called it version number because of this line:
git tag -a <version number here> -m "<my tag name>"
According to here, a specifies the annotation and m the tag message. I will adapt this also to make things clearer.
Do you think it's worth adding a hint to the --follow-tags option?
https://git-scm.com/docs/git-push#Documentation/git-push.txt---follow-tags
Mmh, I'm not sure whether the follow-tags option might complicate things a bit. As I understand it, the codeberg documentation is for a fast and simple introduction to the topic. Thus, I would leave follow-tags to the more interested reader of a deeper introduction to git. What do you think? What was your reason to propose the option?
Nevermind, i was just referencing my use case, but others may have different use cases.
We go with the your proposal, everybody is free to propose additions afterwards.
Thank you very much for your efforts.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?