If you are using Travis to make tests, then a specific environment name for a Travis auth file is also needed, that should be relative to the home directory of your Github repository.
You should then also encrypt the auth file and include the encrypted file in your Github repository. See googlesheets vignette on managing auth tokens and Travis encrypting files how-to for background.
To work on travis, you will need one auth token for the library load in the home folder, and another in the testthat
folder. You can achieve this by using the same encrypted file command twice within your .travis.yml
configuration, writing out to the two different folders:
openssl aes-256-cbc -K $encrypted_0a6446eb3ae3_key -iv $encrypted_0a6446eb3ae3_key -in auth.json.enc -out auth.json -d
openssl aes-256-cbc -K $encrypted_0a6446eb3ae3_key -iv $encrypted_0a6446eb3ae3_key -in auth.json.enc -out tests/testthat/auth.json -d