Grant Timmerman

> So I've just tested that workflow and it does push the deployment up (which was working originally as well) - but it also doesn't make it active as the...

FYI: `clasp redeploy` has been removed in favor of `clasp deploy` with `--` arguments.

It would be nice if we could see the # of API requests: https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list?apix_params=%7B%22name%22%3A%22projects%2Fcounterpoint-test%22%2C%22filter%22%3A%22metric.type%20%3D%20%5C%22storage.googleapis.com%2Fapi%2Frequest_count%5C%22%22%2C%22interval.endTime%22%3A%222018-11-22T00%3A12%3A59Z%22%2C%22interval.startTime%22%3A%222018-11-21T00%3A12%3A59Z%22%7D

It could be a useful command. I don't have any add-ons with significant users, so it's less useful for me. It's a good first issue. Useful for at least for...

@darul75 The original issue seems solved by logging in with a generic Google account. The request described of using non-`$HOME` directory credentials for `push` is a feature request. We currently...

Let us know what your solution is then besides `$HOME`. Putting credentials in a local directory is bad since you'll likely put them in source control, which would be very...

I wrote a proposal of how we could store multiple Google account login creds here: https://github.com/google/clasp/issues/12#issuecomment-370672417 Basically, you can set `settingId`s (`[default/global]`/`"work"`/`"personal"`/`"testGoogleAccount"`) that you can tie to projects. i.e. multilogin...

## Workaround 1: You can `clasp login --creds creds.json` with your own credentials from different profiles if you're interested in working with multiple projects right now. This saves the credentials...

## Solution New flag: ``` clasp login --local ``` Saves `.clasprc.json` locally, but would use global `clasp` credentials. ``` clasp login # global for all projects clasp login --creds creds.json...

We can close after clasp is published and the fix is verified.