We probably won't have Go code to lint or format in this repo, but having Travis run git-validation will help catch whitespace issues and such here before they trickle downstream (e.g. here). By having a .travis.yml in this repo, there's a chance of merge conflicts when pulling template updated into the downstream projects. But I expect the file will be pretty stable and any merge conflicts easy to resolve. If this sounds like a useful direction, I'm happy to work up a PR.