# How to trigger travis build for every commit on master branch?

**URL:** <https://travis-ci.community/t/how-to-trigger-travis-build-for-every-commit-on-master-branch/7487>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [March 8, 2020, 12:11pm UTC](https://travis-ci.community/t/how-to-trigger-travis-build-for-every-commit-on-master-branch/7487 "2020-03-08T12:11:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [March 8, 2020, 3:47pm UTC](https://travis-ci.community/t/how-to-trigger-travis-build-for-every-commit-on-master-branch/7487/2 "2020-03-08T15:47:31Z")

</div>

> [@.travis.yaml file appears to be ignored](https://travis-ci.community/t/travis-yaml-file-appears-to-be-ignored/5019/2):
>
> The file should be called .travis.yml.

You may want to vote on this feature request:

> [@Support the recommended YAML extension of \`.yaml\` for Travis CI project configurations](https://travis-ci.community/t/support-the-recommended-yaml-extension-of-yaml-for-travis-ci-project-configurations/2444):
>
> Travis should natively support the [official YAML standard’s recommended file extension](https://yaml.org/faq.html) of yaml when reading a project’s continuous integration configuration files, allowing developers to use .travis.yaml to define their CI configuration and further enabling developers to have consistency of all their YAML files, while using the recommended extension. Note: This request in no way asks for the current CI configuration filename of .travis.yml to be removed, deprecated, or otherwise changed; the on…

---

_[View the full topic](https://travis-ci.community/t/how-to-trigger-travis-build-for-every-commit-on-master-branch/7487)._