Closed imthenachoman closed 2 years ago
I am closing this issue. I think it doesn't make sense to put credential information in the folder, especially if you're pushing code to a public repo.
I solved my use-case by using VS Codes tasks with the clasp_config_auth
environment variable.
Right now, the auth token is handled globally using
~/.clasprc.json
.I am proposing a new feature where we can save a project specific copy of this file to use for
clasp
commands for that project.So, you could have multiple projects, each using a different account.
Once implemented,
clasp
commands would look for the.clasprc.json
file in the CWD, and then up the folder tree or falling back to the global~/.clasprc.json
.