Another build is triggered if I generate TRAVIS_TAG dynamically

After I implemented a solution from Tagging in after_success script doesn't trigger deployment, do you know why this would happen: https://travis-ci.com/popatop15/TimeMine/builds/141651249?

It executes another build right after the previous one passes and deploys. I imagine this is because of the new tag being pushed? How would I prevent that, but still build each push?

I suppose I could take out tags: true from my .travis.yml, but then deploy would trigger with each push to master. Which I guess I could get over and just develop on another branch. I just didn’t know if there was a way around this without doing that?

Thank you. I wasn’t sure if I should split it into a new post or not since it was directly related to your solution.

Imprint