Old build-number-x tags re-appear about build-number HOT 10 CLOSED

Not sure why that is happening. I just know that I made the script abort the deleting if it found lots of tags because if everything is working properly there should be only one, and when you see unexpected state it's usually not the best course of action to delete everything you see :)

Are you pushing all your local tags to the remote repo or something like that? I'm wondering whether something like that could be causing this.

from build-number.

Sorry, don't know why that happens. Can you check the logs of the last few runs, does it say anything about deleting old tags?

from build-number.

I am getting the same error.

Error: ERROR: Too many my-build-number- refs in repository, found 7, expected only 1. Check your tags!

I check out the repository, modify the source code, and push it.
Then multiple tags are present and an error occurs.

Do I have to delete the old tags locally before pushing?

from build-number.

Problem solved.

I am using Sourcetree as my git client.
The "Push all tags to remotes" setting was turned on.

Thank you for your advice.

from build-number.

Ah, that makes sense. Thanks for letting me know.

from build-number.

I am finding similar cases of this issue in my repositories when Visual Studio is used as the primary git client

from build-number.

@Zyther Ok, is there an option there to not push all tags to remotes?

from build-number.

Thanks all, resolved on my end

from build-number.

Hi guys,
so the solution is to remove all tags? Is there another way to solve this issue in case we need to keep the tags in git repo?

from build-number.

@mitkokostakev really the best solution is to stop using this action and use the $GITHUB_RUN_NUMBER environment variable for build numbers (+ add some offset to it if you need to maintain an old build number).

from build-number.