I think you will need to restrict running lintr to running only on one build. Generally I now recommend running lintr separately, outside of the package tests. You can run it with something like
Thanks @jimhester. Since .lintr is in .Rbuildignore, settings there don't get picked up on Travis. Is your suggested way to specify options in the lint_package call in .travis.yml?
.lintr is still available on travis as long as you don't run it from the built package, e.g. in the tests. The working directory is just a git clone of the repo, so it has all commited files.
Oh, that's helpful on the Travis environment, thanks. For what it's worth, this ended up feeling like more trouble than it was worth -- was getting repeated comments for each commit within a PR and object_length_linter (which I don't adjust anywhere) was behaving differently in and out of testthat -- so I fell back to running tests in testthat on travis and just turning lintr-bot off. Thanks for your help, and for the tool.