> the project's root is the project's, so why does eg the Travis CI system get to insist on having a config file sat in the project root? Because it defines th

> the project's root is the project's, so why does eg the Travis CI system get to insist on having a config file sat in the project root? Because it defines the project's CICI pipeline? Aka how the project is built, tested, delivered, and deployed? I mean, that's a more fundament part of the project than which files should be automatically ignored when committing stuff to git (i.e., .gitignore)