# Specify in travis-yaml project description that it's deprecated in favor of travis-yml

**URL:** <https://travis-ci.community/t/specify-in-travis-yaml-project-description-that-its-deprecated-in-favor-of-travis-yml/4088>\
**Category:** Feature Requests\
**Created:** [July 5, 2019, 3:06pm UTC](https://travis-ci.community/t/specify-in-travis-yaml-project-description-that-its-deprecated-in-favor-of-travis-yml/4088 "2019-07-05T15:06:26Z")\
**Posts on this page:** 1\
**Page:** 1

<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:** [July 5, 2019, 3:06pm UTC](https://travis-ci.community/t/specify-in-travis-yaml-project-description-that-its-deprecated-in-favor-of-travis-yml/4088/1 "2019-07-05T15:06:26Z")

</div>

Subj. At [https://github.com/travis-ci/travis-yaml](https://github.com/travis-ci/travis-yaml), it’s doesn’t say anywhere that it’s no longer used.

A note in the top description along the lines of “DEPRECATED in favor of [https://github.com/travis-ci/travis-yml](https://github.com/travis-ci/travis-yml)” would do the trick in my book.