gigabuddy 0.3.2 → 0.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -2
- package/bin/cli.js +37 -20
- package/index.js +20 -19
- package/package.json +1 -1
- package/src/lib/commands.d.ts +42 -6
package/README.md
CHANGED
|
@@ -34,11 +34,32 @@ credential, and configures `~/.npmrc` for the `@gigabuddy` registry.
|
|
|
34
34
|
| `login` | Sign in and configure `~/.npmrc` for the `@gigabuddy` registry |
|
|
35
35
|
| `login --npm` | Refresh only the npm registry credential |
|
|
36
36
|
| `status` | Show the signed-in account |
|
|
37
|
+
| `accounts` | List accounts on this machine and which is active here |
|
|
38
|
+
| `use <name>` | Use an account for this repo (`--default`: machine-wide) |
|
|
37
39
|
| `doctor [package]` | Diagnose sign-in, npm config, and registry access |
|
|
38
40
|
| `logout` | Sign out (`--npm` removes only the npm credential) |
|
|
39
41
|
|
|
40
|
-
**Options:** `--no-npm` signs in
|
|
41
|
-
targets the staging environment;
|
|
42
|
+
**Options:** `--account <name>` acts as a specific account. `--no-npm` signs in
|
|
43
|
+
without modifying `~/.npmrc`. `--staging` targets the staging environment;
|
|
44
|
+
staging credentials are stored separately.
|
|
45
|
+
|
|
46
|
+
## Multiple accounts
|
|
47
|
+
|
|
48
|
+
Sign in more than one identity (say, personal and work) and choose which one a
|
|
49
|
+
repository uses:
|
|
50
|
+
|
|
51
|
+
```bash
|
|
52
|
+
gigabuddy login --account work # sign a second identity in
|
|
53
|
+
gigabuddy use work # this repo (worktrees included) acts as it
|
|
54
|
+
gigabuddy use --default work # or make it the machine-wide default
|
|
55
|
+
gigabuddy accounts # who is signed in, and which is active here
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Which account is active resolves as: the `GIGABUDDY_ACCOUNT` environment
|
|
59
|
+
variable, then the closest repo pin (set by `gigabuddy use`), then your
|
|
60
|
+
default account. Each account keeps its own credentials under `~/.gigabuddy`;
|
|
61
|
+
the npm credential in `~/.npmrc` is machine-wide and follows whichever
|
|
62
|
+
account ran `login` last.
|
|
42
63
|
|
|
43
64
|
## Credentials
|
|
44
65
|
|