# "Skipping a deployment with the releases provider because this is not a tagged commit" despite me creating a tag

**URL:** <https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581>\
**Category:** Deployment\
**Tags:** deploy-conditions\
**Created:** [October 21, 2019, 10:28am UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581 "2019-10-21T10:28:54Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![filimo](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@filimo](https://travis-ci.community/u/filimo)\
**Post date:** [October 21, 2019, 10:28am UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/1 "2019-10-21T10:28:54Z")

</div>

I try to deploy a build to GitHub.

I add a tag like “v1.3.13” and the script is running I get the error “Skipping a deployment with the releases provider because this is not a tagged commit”

My [.travis.yml](https://github.com/filimo/ReaderTranslator/blob/master/.travis.yml)

Whats am I doing wrong?

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [October 21, 2019, 12:37pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/2 "2019-10-21T12:37:54Z")

</div>

There is no tag matching [this regular expression](https://github.com/filimo/ReaderTranslator/blob/21ce273b1ca2d648bb46eced509572e783bfe2fe/.travis.yml#L39) pushed to GitHub. [https://github.com/filimo/ReaderTranslator/releases](https://github.com/filimo/ReaderTranslator/releases).

You’ll have to modify the regular expression (or change your tag naming scheme) and push new tags.

---

<div class="post-metadata">

**Author:** ![filimo](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@filimo](https://travis-ci.community/u/filimo)\
**Post date:** [October 21, 2019, 1:49pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/3 "2019-10-21T13:49:13Z")

</div>

I pushed the last commit with tag \* [v1.3.13](https://github.com/filimo/ReaderTranslator/releases/tag/v1.3.13) and it wasn’t appeared in [https://github.com/filimo/ReaderTranslator/releases](https://github.com/filimo/ReaderTranslator/releases).  
After your answer I went to the release page and rename the last tag with v1.3.13 and clicked on `Restart build` in `Travis CI`.  
After the build was finished I again saw the same error.

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [October 21, 2019, 2:30pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/4 "2019-10-21T14:30:21Z")

</div>

I don’t think renaming the tags on GitHub has the desired effect. You’ll have to push a tag with the matching pattern to GitHub.

---

<div class="post-metadata">

**Author:** ![filimo](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@filimo](https://travis-ci.community/u/filimo)\
**Post date:** [October 21, 2019, 4:00pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/5 "2019-10-21T16:00:46Z")

</div>

I pushed new commit with v1.13.14 tag. Result was same.

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [October 21, 2019, 4:04pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/6 "2019-10-21T16:04:07Z")

</div>

We are not getting any build request associated with the pushed tag. [https://travis-ci.com/filimo/ReaderTranslator/requests](https://travis-ci.com/filimo/ReaderTranslator/requests)

---

<div class="post-metadata">

**Author:** ![filimo](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@filimo](https://travis-ci.community/u/filimo)\
**Post date:** [October 21, 2019, 4:11pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/7 "2019-10-21T16:11:30Z")

</div>

I see `master 20b53c8` request with tag `v1.3.14`

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [October 21, 2019, 4:16pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/8 "2019-10-21T16:16:33Z")

</div>

That’s for the `master` branch request, which will not trigger deployment.

---

<div class="post-metadata">

**Author:** ![filimo](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@filimo](https://travis-ci.community/u/filimo)\
**Post date:** [October 21, 2019, 4:21pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/9 "2019-10-21T16:21:39Z")

</div>

Do you mean I have to create branch called `v1.3.14`?

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [October 21, 2019, 4:25pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/10 "2019-10-21T16:25:44Z")

</div>

No. I mean that when you push the tag to GitHub with `git push --tags`, we should receive the notification and run the build, but I don’t see the evidence of this happening.

---

<div class="post-metadata">

**Author:** ![filimo](https://avatars.discourse-cdn.com/v4/letter/f/7ba0ec/32.png) [@filimo](https://travis-ci.community/u/filimo)\
**Post date:** [October 21, 2019, 6:50pm UTC](https://travis-ci.community/t/skipping-a-deployment-with-the-releases-provider-because-this-is-not-a-tagged-commit-despite-me-creating-a-tag/5581/11 "2019-10-21T18:50:21Z")

</div>

I think the problem was with Xcode when I create tag and push the commit with doing turn `Include tags` on.  
When I did it in terminal everything went smoothly. Thanks.
