• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Git
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      In our repository we use Git Tags to tag which code is deployed on specific environment (TEST, UAT, PROD).

      Whenever we make another deployment on enviroment we use the same Tag name (basically this means that old tag is deleted and new is created on different commit).

       

      If another developer wants to refresh the tags, he uses Fetch / Fetch all tags using Sourcetree.

       

      Since tag has the same name we get the following error:

      "git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks fetch --prune --tags origin
      _From https://dev.azure.com/GeniDevOps/Integrations/_git/NeuronEsbSales_
      ! [rejected] TEST-Sales -> TEST-Sales (would clobber existing tag)

      Completed with errors, see above."

       

      Doing some research we found out that as of Git 2.2.0 you need to explicitly specify the force flag:

      git fetch origin --tags --force

      source: https://stackoverflow.com/questions/9662249/how-to-overwrite-local-tags-with-git-fetch/21475727

       

      Can you please add this option to force fatching the tags to Sourcetree?

            [SRCTREE-7077] Add option to force fetching of tags with the same name

            Mochnant added a comment - - edited

            +1 to this.  I could also use the functionality when tags are changed upstream.

            Note this would be useful for both Windows and Mac versions.

            Mochnant added a comment - - edited +1 to this.  I could also use the functionality when tags are changed upstream. Note this would be useful for both Windows and Mac versions.

            Carlo Accorsi added a comment - - edited

            Yes,  I have the same issue as the other posters.

            Ideally a checkbox option would enable the default behavior and do the equivalent of --force for the pull with tags. thx

            Carlo Accorsi added a comment - - edited Yes,  I have the same issue as the other posters. Ideally a checkbox option would enable the default behavior and do the equivalent of --force for the pull with tags. thx

            Clark added a comment - - edited

            If you want to play on a quality and reliable site in Bangladesh, then this site - https://mcw-bangladesh.com/ - will come to your rescue. I've been playing on this site for a long time, because it's the only one that has all my favourite slot games in Bangladesh. Also, this site has fast transactions, which makes using this site even more enjoyable.

            Clark added a comment - - edited If you want to play on a quality and reliable site in Bangladesh, then this site - https://mcw-bangladesh.com/ - will come to your rescue. I've been playing on this site for a long time, because it's the only one that has all my favourite slot games in Bangladesh. Also, this site has fast transactions, which makes using this site even more enjoyable.

            We have a similar case, any idea if this is going to be implemented?

            As for now, we need to use run git pull --tags -f in the terminal to fix this error every time a tag is moved

            Amir Rossert added a comment - We have a similar case, any idea if this is going to be implemented? As for now, we need to use run git pull --tags -f in the terminal to fix this error every time a tag is moved

              Unassigned Unassigned
              19b05432475f thelovro
              Votes:
              31 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: