I'd like to deploy files using Travis CI and it only works for a tagged commit. When committing to the branch, there is a warning:

Skipping a deployment with the releases provider because this is not a tagged commit.

Is there any way to deploy on branched commit using Travis CI?

To clarify, it works when I tag the commit, but I'd like to deploy files on each commit for the given branch.

  • 1
    Have you tried tagging the commit? Commented Feb 28, 2017 at 18:20
  • It works for the tags, but I'd like to deploy files on every commit.
    – kenorb
    Commented Feb 28, 2017 at 18:20

2 Answers 2


Instead of using Travis' deployment features, build the deployment logic in to your normal "test" script(s). For a PaaS this might be as simple as pushing to another git remote if all tests pass, but the sky is the limit.


Travis CI supports deployment on branch release by using the following syntax:

    branch: release

The problem is that GitHub does not support it.

As per GitHub Releases Uploading page at Travis CI:

Please note that deploying GitHub Releases works only for tags, not for branches.

For GitHub the only workaround is to push tags (e.g. git push origin master --tags).

Or solution is to use different supported provider.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.