Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

[QUESTION] Why i cannot tag 1.0.0 if i have "re-inited" my new "master" to a new branch? #468

Open
oscaraparicio77 opened this issue Oct 22, 2021 · 3 comments

Comments

@oscaraparicio77
Copy link

oscaraparicio77 commented Oct 22, 2021

Hi there.

First, i'm not an expert, but congrats for this project.

I have done some tests with merges from develop to master wth tags successfully, i use this steps:

git checkout develop
git flow release start $VERSION
git add .
git flow release finish -F -m "Tag" $VERSION
git checkout master && git push origin master
git push origin $VERSION
git checkout develop && git push origin develop

Now, if i do a

git flow init -f to change the "master" brach to another branch, i cannot tag 1.0.0 version if i was used 1.0.0 version in default master branch.

I want to have a 1.0.0 tag in many branches, basically.

Can i archieve this goal in any way?

@oscaraparicio77
Copy link
Author

Nodoby? :-(

@oscaraparicio77
Copy link
Author

Is gitflow-avh capable of do this? please, some help is appreciated

@Serhioromano
Copy link

When you add tag, it is not git flow specific tag, it is ordinary git tag. Git tags are not related to branches. It is a separate tree. So, you cannot create 2 same name tags in a single repository. This is the limitation of Git itself.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants