Who's Travis?

I remember seeing a talk or listening to a podcast during which they mentioned Travis, as in the CI pipeline tool, and some of the things they were using it for.

They also said that their client thought Travis was a person on their team.

In some ways, having a CI pipeline performing automated checks and tests is like having another team member.

Instead of waiting for a person to manually check code styles, run tests and spot potential bugs, why not automate them and run them in the CI pipeline every time code changes are pushed?

You'll get results sooner than waiting for a person do check the code by hand and, arguably, more consistent results.

Then, if you do peer code reviews, you know the basics are already done and the reviewer can focus on other things.