# About the Build Config Validation category

**URL:** <https://travis-ci.community/t/about-the-build-config-validation-category/5494>\
**Category:** Build Config Validation\
**Created:** [October 16, 2019, 6:26pm UTC](https://travis-ci.community/t/about-the-build-config-validation-category/5494 "2019-10-16T18:26:40Z")\
**Posts on this page:** 2\
**Page:** 1

<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 16, 2019, 6:26pm UTC](https://travis-ci.community/t/about-the-build-config-validation-category/5494/1 "2019-10-16T18:26:40Z")

</div>

Use this category for reporting issues and requests with the upcoming configuration validator feature. For more details, see

> **[Travis CI Documentation](https://docs.travis-ci.com/user/build-config-validation)**
>
> Build Config Validation

---

<div class="post-metadata">

**Author:** ![ssbarnea](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/ssbarnea/32/415_2.png) [@ssbarnea](https://travis-ci.community/u/ssbarnea)\
**Post date:** [October 25, 2019, 5:05pm UTC](https://travis-ci.community/t/about-the-build-config-validation-category/5494/2 "2019-10-25T17:05:53Z")

</div>

travis lint should be exposed as a pre-commit hook, so people can easily lint alongside other linters. See [https://pre-commit.com/](https://pre-commit.com/)

Exposing a tool as a hook requires just adding a simple yaml file to its repository.

I created [https://github.com/pre-commit/pre-commit/issues/1189](https://github.com/pre-commit/pre-commit/issues/1189) for tracking but keep in mind that is not the pre-commit tool that needs to add the hook definition.