@mattpolzin/harmony 5.5.1 → 5.7.0
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 +194 -67
- package/harmony +779 -608
- package/man/harmony.1 +23 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
% harmony(1) Version 5.
|
|
1
|
+
% harmony(1) Version 5.7.0 | Harmony User's Guide
|
|
2
2
|
|
|
3
3
|
# NAME
|
|
4
4
|
Harmony - Harmonize with coworkers around GitHub reviewing
|
|
@@ -22,23 +22,35 @@ Harmony - Harmonize with coworkers around GitHub reviewing
|
|
|
22
22
|
`harmony whoami`
|
|
23
23
|
|
|
24
24
|
# DESCRIPTION
|
|
25
|
-
Harmony is a small tool that helps teams keep GitHub reviews running smoothly.
|
|
25
|
+
Harmony is a small tool that helps teams keep GitHub reviews running smoothly.
|
|
26
|
+
It takes the work out of picking someone from a pool of developers to review a
|
|
27
|
+
new PR. Harmony does this by heuristically determining who on a particular
|
|
28
|
+
GitHub Team has the least current/recent review workload.
|
|
26
29
|
|
|
27
|
-
Harmony offers a heuristic for PR review requests that is different than
|
|
30
|
+
Harmony offers a heuristic for PR review requests that is different than
|
|
31
|
+
GitHub's round robin or weighted algorithms, but Harmony can also work well even
|
|
32
|
+
if your team uses GitHub's automatic PR review requests ([see below](#deferring-to-github)).
|
|
28
33
|
|
|
29
34
|
## Dependencies
|
|
30
35
|
### Runtime
|
|
31
|
-
Running Harmony requires NodeJS 18+ (and a local installation of `git`) or
|
|
36
|
+
Running Harmony requires NodeJS 18+ (and a local installation of `git`) or
|
|
37
|
+
alternatively Nix with flakes enabled.
|
|
32
38
|
|
|
33
|
-
If you'd like to try Harmony out without even "installing" it and you have Nix
|
|
39
|
+
If you'd like to try Harmony out without even "installing" it and you have Nix
|
|
40
|
+
installed with flakes enabled, you can run it as
|
|
41
|
+
`nix run github:mattpolzin/harmony`.
|
|
34
42
|
|
|
35
43
|
### Build time
|
|
36
|
-
Building the latest commits of Harmony requires a HEAD build of the Idris 2
|
|
44
|
+
Building the latest commits of Harmony requires a HEAD build of the Idris 2
|
|
45
|
+
compiler. Each release page also indicates the version of Idris 2 that
|
|
46
|
+
particular release will build against.
|
|
37
47
|
|
|
38
|
-
Alternatively, you can build Harmony with Docker (see
|
|
48
|
+
Alternatively, you can build Harmony with Docker (see
|
|
49
|
+
[Docker Build](#docker-build)).
|
|
39
50
|
|
|
40
51
|
## Installation
|
|
41
|
-
For any installation, you need to have a GitHub
|
|
52
|
+
For any installation, you need to have a GitHub
|
|
53
|
+
[Personal Access Token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
|
42
54
|
|
|
43
55
|
Your Personal Access Token should have the following permissions:
|
|
44
56
|
- `repo` (Full control of private repositories)
|
|
@@ -48,13 +60,21 @@ Your Personal Access Token should have the following permissions:
|
|
|
48
60
|
- `read:discussion`
|
|
49
61
|
- `read:enterprise` (Read enterprise profile data)
|
|
50
62
|
|
|
51
|
-
You can either add the PAT to your environment as the `GITHUB_PAT` (or
|
|
63
|
+
You can either add the PAT to your environment as the `GITHUB_PAT` (or
|
|
64
|
+
alternatively `GH_TOKEN`) variable (perhaps exporting it from your shell
|
|
65
|
+
resource file or profile) or you can store your PAT in Harmony's config file.
|
|
66
|
+
The first time you start Harmony, it will ask you to configure your PAT if you
|
|
67
|
+
don't want to use the Environment variable. You only need one of (a) the ENV var
|
|
68
|
+
and (b) the config property and the environment variable will take precedence if
|
|
69
|
+
you have both set.
|
|
52
70
|
|
|
53
71
|
### NPM
|
|
54
|
-
You can install Harmony via npm directly by running
|
|
72
|
+
You can install Harmony via npm directly by running
|
|
73
|
+
`npm install -g @mattpolzin/harmony`.
|
|
55
74
|
|
|
56
75
|
### GitHub Release
|
|
57
|
-
You can install any Harmony release by downloading the `harmony-npm.tar.gz` file
|
|
76
|
+
You can install any Harmony release by downloading the `harmony-npm.tar.gz` file
|
|
77
|
+
from the GitHub Release page, unzipping it, and running `npm install --global`.
|
|
58
78
|
|
|
59
79
|
### Nix Flake
|
|
60
80
|
You can add Harmony to your Flake inputs as follows:
|
|
@@ -66,7 +86,8 @@ You can add Harmony to your Flake inputs as follows:
|
|
|
66
86
|
};
|
|
67
87
|
```
|
|
68
88
|
|
|
69
|
-
Then, in your outputs, bring Harmony into a package install list as
|
|
89
|
+
Then, in your outputs, bring Harmony into a package install list as
|
|
90
|
+
`harmony.packages.<system>.harmony`.
|
|
70
91
|
|
|
71
92
|
Harmony builds are cached in Cachix so you can take advantage of those builds by
|
|
72
93
|
adding `https://gh-harmony.cachix.org` to the list of `substituters` and
|
|
@@ -74,12 +95,16 @@ adding `https://gh-harmony.cachix.org` to the list of `substituters` and
|
|
|
74
95
|
list of `trusted-public-keys`.
|
|
75
96
|
|
|
76
97
|
### From Source
|
|
77
|
-
The build script assumes a HEAD build of Idris 2 is installed on your system.
|
|
98
|
+
The build script assumes a HEAD build of Idris 2 is installed on your system.
|
|
99
|
+
For an alternative, see the [Docker Build](#docker-build) instructions below.
|
|
78
100
|
|
|
79
|
-
Build Harmony from source with a call to `make`. Then install it globally with
|
|
101
|
+
Build Harmony from source with a call to `make`. Then install it globally with
|
|
102
|
+
`make install`.
|
|
80
103
|
|
|
81
104
|
### Docker Build
|
|
82
|
-
If you want to build Harmony without installing Idris 2 on your system, you can
|
|
105
|
+
If you want to build Harmony without installing Idris 2 on your system, you can
|
|
106
|
+
build Harmony within a Docker container and then install the resulting
|
|
107
|
+
Javascript onto your system.
|
|
83
108
|
|
|
84
109
|
First, download the latest nightly Docker image:
|
|
85
110
|
```shell
|
|
@@ -93,27 +118,36 @@ docker run --rm -v "$(pwd):/build" \
|
|
|
93
118
|
bash -c "apt-get update && apt-get install -y git && cd /build && make"
|
|
94
119
|
```
|
|
95
120
|
|
|
96
|
-
At this point you are done with Docker. From the same directory, install Harmony
|
|
121
|
+
At this point you are done with Docker. From the same directory, install Harmony
|
|
122
|
+
globally:
|
|
97
123
|
```shell
|
|
98
124
|
npm install --global
|
|
99
125
|
```
|
|
100
126
|
|
|
101
127
|
### Bash completion
|
|
102
|
-
Set up Bash completion by adding the following to your Bash resource file or
|
|
128
|
+
Set up Bash completion by adding the following to your Bash resource file or
|
|
129
|
+
profile:
|
|
103
130
|
```shell
|
|
104
131
|
eval "$(harmony --bash-completion-script)"
|
|
105
132
|
```
|
|
106
133
|
|
|
107
134
|
### Zsh completion
|
|
108
|
-
Zsh completion is supported via `bashcompinit` and can be loaded by adding the
|
|
135
|
+
Zsh completion is supported via `bashcompinit` and can be loaded by adding the
|
|
136
|
+
following to your Zsh resource file or profile:
|
|
109
137
|
```shell
|
|
110
138
|
eval "$(harmony --zsh-completion-script)"
|
|
111
139
|
```
|
|
112
140
|
|
|
113
141
|
## Usage
|
|
114
|
-
The first time you start Harmony in any particular folder, you will be asked to
|
|
115
|
-
|
|
116
|
-
|
|
142
|
+
The first time you start Harmony in any particular folder, you will be asked to
|
|
143
|
+
provide some information about the GitHub repository you are working with. This
|
|
144
|
+
information is stored in a file named `harmony.json` in the current working
|
|
145
|
+
directory.
|
|
146
|
+
|
|
147
|
+
Note that the GitHub organization and repository are both slugs, not names.
|
|
148
|
+
These are the values you find in a GitHub URL pointing to your repository.
|
|
149
|
+
Harmony works with personal repositories but some of Harmony's features are not
|
|
150
|
+
available for these repos because they do not have teams or members.
|
|
117
151
|
```
|
|
118
152
|
$ harmony sync
|
|
119
153
|
Creating a new configuration (storing in harmony.json)...
|
|
@@ -136,20 +170,30 @@ Would you like harmony to request team reviews in addition to individuals when i
|
|
|
136
170
|
Creating config...
|
|
137
171
|
```
|
|
138
172
|
|
|
139
|
-
Once configured, Harmony supports the following commands: `config`, `branch`,
|
|
173
|
+
Once configured, Harmony supports the following commands: `config`, `branch`,
|
|
174
|
+
`pr`, `quick`, `label`, `request` (also aliased to `rq`), `contribute`,
|
|
175
|
+
`whoami`, `reflect`, `list`, `graph`, `health`, and `sync`.
|
|
140
176
|
|
|
141
177
|
**Note on color output:**
|
|
142
|
-
Harmony uses colored output for some commands. You can adjust these colors
|
|
178
|
+
Harmony uses colored output for some commands. You can adjust these colors
|
|
179
|
+
slightly with the `theme` configuration option. You can also use the `NO_COLOR`
|
|
180
|
+
environment variable to disable all colored output. Lastly, Harmony will avoid
|
|
181
|
+
colored output when it determines `stdout` is not a TTY device (as is the case
|
|
182
|
+
for e.g. redirecting harmony output into a file or piping into `cat`:
|
|
183
|
+
`harmony ... | cat`).
|
|
143
184
|
|
|
144
185
|
# SUBCOMMANDS
|
|
145
186
|
|
|
146
187
|
## `branch`
|
|
147
188
|
Print the URI for accessing the currently checked out branch on GitHub.
|
|
148
189
|
|
|
149
|
-
Many operating systems have an `open` command (though the name "open" is not
|
|
190
|
+
Many operating systems have an `open` command (though the name "open" is not
|
|
191
|
+
ubiquitous); this means you can run something like `open $(harmony branch)` to
|
|
192
|
+
open a web browser to the current branch on GitHub.
|
|
150
193
|
|
|
151
194
|
## `config {property} [value]`
|
|
152
|
-
Read the given configuration property. `harmony config <property> <value>` will
|
|
195
|
+
Read the given configuration property. `harmony config <property> <value>` will
|
|
196
|
+
set the configuration property.
|
|
153
197
|
|
|
154
198
|
Not all configuration properties can be read/set with this command.
|
|
155
199
|
|
|
@@ -180,30 +224,47 @@ Not all configuration properties can be read/set with this command.
|
|
|
180
224
|
: If the `$GITHUB_PAT` and `$GH_TOKEN` environment variables are not set, this Personal Access Token is used to authenticate with GitHub.
|
|
181
225
|
|
|
182
226
|
## `contribute [options]`
|
|
183
|
-
Print the URI of the oldest non-draft PR waiting for your review. If you are not
|
|
227
|
+
Print the URI of the oldest non-draft PR waiting for your review. If you are not
|
|
228
|
+
requested for review on any PRs, Harmony will suggest a PR that your review is
|
|
229
|
+
not requested on.
|
|
184
230
|
|
|
185
|
-
You can skip PRs and retrieve the next-oldest one by passing a dash followed by
|
|
231
|
+
You can skip PRs and retrieve the next-oldest one by passing a dash followed by
|
|
232
|
+
the number to skip (e.g. `-2` to skip the two oldest waiting PRs).
|
|
186
233
|
|
|
187
|
-
You can also more permanently ignore a particular PR (perhaps it has gone
|
|
234
|
+
You can also more permanently ignore a particular PR (perhaps it has gone
|
|
235
|
+
stagnant but your org does not want to close it for whatever reason). To do
|
|
236
|
+
this, use the `--ignore` or `-i` option and pass it the GitHub URI or the Pull
|
|
237
|
+
Request Number of a PR to ignore. This PR will be omitted from consideration for
|
|
238
|
+
the `contribute` command from then on. This only impacts your local machine
|
|
239
|
+
where the ignore list is stored in Harmony's config file.
|
|
188
240
|
|
|
189
|
-
You can simultaneously get the URI for a PR to review and checkout the branch
|
|
241
|
+
You can simultaneously get the URI for a PR to review and checkout the branch
|
|
242
|
+
needing review by passing the `--checkout` or `-c` option to the `contribute`
|
|
243
|
+
command.
|
|
190
244
|
|
|
191
|
-
Many operating systems have an `open` command (though the name "open" is not
|
|
245
|
+
Many operating systems have an `open` command (though the name "open" is not
|
|
246
|
+
ubiquitous); this means you can run something like `open $(harmony contribute)`
|
|
247
|
+
to open a web browser to the PR that Harmony is suggesting.
|
|
192
248
|
|
|
193
|
-
You can also run `harmony contribute --list` if you want to list out a few PRs
|
|
249
|
+
You can also run `harmony contribute --list` if you want to list out a few PRs
|
|
250
|
+
to consider reviewing them instead of choosing just one PR to look into and
|
|
251
|
+
printing that PRs URI.
|
|
194
252
|
|
|
195
253
|
### Examples
|
|
196
|
-
Retrieve a URI for the oldest unreviewed and open PR (prioritizing PRs for which
|
|
254
|
+
Retrieve a URI for the oldest unreviewed and open PR (prioritizing PRs for which
|
|
255
|
+
you are a requested reviewer):
|
|
197
256
|
```shell
|
|
198
257
|
harmony contribute
|
|
199
258
|
```
|
|
200
259
|
|
|
201
|
-
Retrieve a URI for a PR to contribute a review, skipping over the first 3
|
|
260
|
+
Retrieve a URI for a PR to contribute a review, skipping over the first 3
|
|
261
|
+
suggestions:
|
|
202
262
|
```shell
|
|
203
263
|
harmony contribute -3
|
|
204
264
|
```
|
|
205
265
|
|
|
206
|
-
Retrieve a URI for a PR to contribute a review and check the git branch out as
|
|
266
|
+
Retrieve a URI for a PR to contribute a review and check the git branch out as
|
|
267
|
+
well:
|
|
207
268
|
```shell
|
|
208
269
|
harmony contribute --checkout
|
|
209
270
|
```
|
|
@@ -219,14 +280,18 @@ harmony contribute --ignore 1234
|
|
|
219
280
|
```
|
|
220
281
|
|
|
221
282
|
## `graph [--completed] {team-slug}`
|
|
222
|
-
Graph the relative review workload of each of the members of the given GitHub
|
|
283
|
+
Graph the relative review workload of each of the members of the given GitHub
|
|
284
|
+
Team.
|
|
223
285
|
|
|
224
|
-
You can optionally graph completed PR reviews with the `--completed` flag as
|
|
286
|
+
You can optionally graph completed PR reviews with the `--completed` flag as
|
|
287
|
+
well, though these are not considered for Harmony's weighting algorithm for
|
|
288
|
+
review workload.
|
|
225
289
|
|
|
226
290
|
## `health`
|
|
227
291
|
Graph all open PRs grouped by the month when each was created.
|
|
228
292
|
|
|
229
|
-
The idea is that a healthy repository does not have many old PRs still open
|
|
293
|
+
The idea is that a healthy repository does not have many old PRs still open
|
|
294
|
+
because those PRs represent effort spent by developers that hasn't yet paid off.
|
|
230
295
|
|
|
231
296
|
|
|
232
297
|
|
|
@@ -234,25 +299,54 @@ The idea is that a healthy repository does not have many old PRs still open beca
|
|
|
234
299
|
Print help.
|
|
235
300
|
|
|
236
301
|
## `label {label} [...]`
|
|
237
|
-
Helps you create a PR if one does not exist yet and then it will apply the given
|
|
302
|
+
Helps you create a PR if one does not exist yet and then it will apply the given
|
|
303
|
+
labels to the PR. This is essentially an alias for the `harmony pr` command but
|
|
304
|
+
without support for creating draft PRs.
|
|
238
305
|
|
|
239
|
-
Note that labels are _not_ prefixed with '#' for this command. There is no need
|
|
306
|
+
Note that labels are _not_ prefixed with '#' for this command. There is no need
|
|
307
|
+
to differentiate labels from other kinds of arguments to `harmony label`.
|
|
240
308
|
|
|
241
309
|
## `list [team-slug]`
|
|
242
|
-
Running `harmony list` will list all the teams for the configured GitHub
|
|
310
|
+
Running `harmony list` will list all the teams for the configured GitHub
|
|
311
|
+
organization.
|
|
243
312
|
|
|
244
313
|
Running `harmony list <team>` will list the members of the given GitHub Team.
|
|
245
314
|
|
|
246
|
-
## `pr [--draft] [#label, ...]`
|
|
247
|
-
With a branch checked out will reach out to GitHub to determine if there is an
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
|
|
251
|
-
|
|
252
|
-
|
|
253
|
-
If you
|
|
254
|
-
|
|
255
|
-
|
|
315
|
+
## `pr [--draft] [-i/--into {<branch-name>}] [#label, ...]`
|
|
316
|
+
With a branch checked out will reach out to GitHub to determine if there is an
|
|
317
|
+
open PR for that branch. If there is a PR, Harmony will print a URI that can be
|
|
318
|
+
used to view the PR. If there is not a PR, Harmony will help you create one. New
|
|
319
|
+
and existing PRs can be marked as drafts by specifying the `--draft` flag with
|
|
320
|
+
the `pr` command.
|
|
321
|
+
|
|
322
|
+
If you need to create a PR still, you will be prompted for a branch to open the
|
|
323
|
+
PR against (merge into, eventually), a title for the PR, and a description for
|
|
324
|
+
the PR. If you have an `EDITOR` environment variable set, Harmony will use that
|
|
325
|
+
editor to get the PR description from you. If you have a PR template at
|
|
326
|
+
`.github/PULL_REQUEST_TEMPLATE.md`, Harmony will also preload that into your
|
|
327
|
+
editor. If you do not have an `EDITOR` environment variable set, you will still
|
|
328
|
+
be able to enter a description from the command line but PR templates are only
|
|
329
|
+
supported when an `EDITOR` is specified.
|
|
330
|
+
|
|
331
|
+
If you are creating a new PR from a branch that refers to a GitHub issue (and
|
|
332
|
+
you have GitHub branch parsing enabled in your harmony config) then harmony will
|
|
333
|
+
prepend the issue information onto your new PR description in a commented out
|
|
334
|
+
block for you to reference or copy into the PR description as needed.
|
|
335
|
+
|
|
336
|
+
You can specify the branch to merge into via the `--into` CLI argument if you
|
|
337
|
+
want to as an alternative to the interactive prompt.
|
|
338
|
+
|
|
339
|
+
You can also specify any number of labels to apply by prefixing them with '#'.
|
|
340
|
+
For example, `harmony pr #backport #bugfix` would create a PR and apply the
|
|
341
|
+
`backport` and `bugfix` labels.
|
|
342
|
+
|
|
343
|
+
If you are using harmony from a script or some other environment without TTY
|
|
344
|
+
support, harmony will print a GitHub URL that can be used to create the PR. This
|
|
345
|
+
mode of operation will ignore the `--draft` and `#label` options.
|
|
346
|
+
|
|
347
|
+
Many operating systems have an `open` command (though the name "open" is not
|
|
348
|
+
ubiquitous); this means you can run something like `open $(harmony pr)` to open
|
|
349
|
+
a web browser to an existing PR for the current branch.
|
|
256
350
|
|
|
257
351
|
### Examples
|
|
258
352
|
Create a draft pull request for the current branch:
|
|
@@ -265,11 +359,20 @@ Create a PR for the current branch and add the `urgent` label:
|
|
|
265
359
|
harmony pr #urgent
|
|
266
360
|
```
|
|
267
361
|
|
|
268
|
-
|
|
269
|
-
|
|
270
|
-
|
|
271
|
-
|
|
272
|
-
|
|
362
|
+
Create a pull request that will merge into the hypothetical pre-existing
|
|
363
|
+
`release/2_0` branch:
|
|
364
|
+
```shell
|
|
365
|
+
harmony pr --into release/2_0
|
|
366
|
+
```
|
|
367
|
+
|
|
368
|
+
## `quick [--bugfix]`
|
|
369
|
+
Helps you create a new GitHub issue and a branch to work on that issue all in
|
|
370
|
+
one go. The branch name will be structured such that if you have GitHub branch
|
|
371
|
+
parsing on then the PR you create for the branch later on will refer to the
|
|
372
|
+
issue created now.
|
|
373
|
+
|
|
374
|
+
By default the branch created will be prefixed with `feature` but if you specify
|
|
375
|
+
the `--bugfix` flag then the branch's prefix will be `bugfix`.
|
|
273
376
|
|
|
274
377
|
## `reflect`
|
|
275
378
|
Show a summary of your review requests and authored pull requests.
|
|
@@ -277,42 +380,66 @@ Show a summary of your review requests and authored pull requests.
|
|
|
277
380
|
|
|
278
381
|
|
|
279
382
|
## `request {team-slug | +user-login} [options]`
|
|
280
|
-
Helps you create a PR if one does not exist yet and then it will request reviews
|
|
383
|
+
Helps you create a PR if one does not exist yet and then it will request reviews
|
|
384
|
+
from teams and/or users.
|
|
281
385
|
|
|
282
386
|
There is also a `harmony rq` alias for `harmony request`.
|
|
283
387
|
|
|
284
|
-
If `harmony config requestUsers` is `True` (defualt) then harmony will pick
|
|
285
|
-
|
|
286
|
-
|
|
287
|
-
|
|
288
|
-
|
|
388
|
+
If `harmony config requestUsers` is `True` (defualt) then harmony will pick
|
|
389
|
+
someone to review the PR (from one of the listed teams). If `harmony config
|
|
390
|
+
requestTeams` is `True` (default) then harmony will request reviews from the
|
|
391
|
+
teams you listed. If `harmony config commentOnRequest` is `True` then harmony
|
|
392
|
+
will comment on the Pull Request indicating that teams & users were
|
|
393
|
+
"harmoniously requested" -- this comment will @mention requested users so it may
|
|
394
|
+
be useful or annoying depending on the requested user's GitHub notification
|
|
395
|
+
settings.
|
|
396
|
+
|
|
397
|
+
You can also require that specific additional users (on top of the one Harmony
|
|
398
|
+
will pick for you) are requested to review the PR. You do this by specifying
|
|
399
|
+
those users' logins prefixed with '+' as arguments to Harmony. This will request
|
|
400
|
+
review from those specific additional users regardless of the `requestUsers`
|
|
401
|
+
setting; that setting controls whether Harmony picks users from each Team you
|
|
402
|
+
specify to review PRs.
|
|
403
|
+
|
|
404
|
+
You can optionally apply any number of labels to the PR at the same time as
|
|
405
|
+
requesting reviewers by prefixing the labels with '#'.
|
|
289
406
|
|
|
290
407
|
### Deferring to GitHub
|
|
291
|
-
If your team has GitHub set up to auto-request reviews from individuals when a
|
|
408
|
+
If your team has GitHub set up to auto-request reviews from individuals when a
|
|
409
|
+
team is requested for review, you probably want to tell harmony not to also pick
|
|
410
|
+
someone using its heuristics. You can run the following `config` commands to
|
|
411
|
+
tell harmony to request a team but not also pick an individual from that team:
|
|
292
412
|
```shell
|
|
293
413
|
harmony config requestTeams true
|
|
294
414
|
harmony config requestUsers false
|
|
295
415
|
```
|
|
296
|
-
This does not prevent you from requesting specific individuals with the
|
|
416
|
+
This does not prevent you from requesting specific individuals with the
|
|
417
|
+
`+<user>` syntax described above.
|
|
297
418
|
|
|
298
419
|
### Examples
|
|
299
|
-
Request review from the most available reviewer from the "developers" GitHub
|
|
420
|
+
Request review from the most available reviewer from the "developers" GitHub
|
|
421
|
+
Team:
|
|
300
422
|
```shell
|
|
301
423
|
harmony request developers
|
|
302
424
|
```
|
|
303
425
|
|
|
304
|
-
Request review from the most available reviewer from either the "frontend" or
|
|
426
|
+
Request review from the most available reviewer from either the "frontend" or
|
|
427
|
+
"backend" GitHub Team:
|
|
305
428
|
```shell
|
|
306
429
|
harmony request frontend backend
|
|
307
430
|
```
|
|
308
431
|
|
|
309
|
-
Request review from the most available reviewer from the "web" team and
|
|
432
|
+
Request review from the most available reviewer from the "web" team and
|
|
433
|
+
additionally request review from the users with logins "carl001" and "emmaham":
|
|
310
434
|
```shell
|
|
311
435
|
harmony request web +carl001 +emmaham
|
|
312
436
|
```
|
|
313
437
|
|
|
314
438
|
## `sync`
|
|
315
|
-
Sync the locally configured team slugs and user logins that are used by
|
|
439
|
+
Sync the locally configured team slugs and user logins that are used by
|
|
440
|
+
auto-completion for Harmony. This sync is also performed automatically the first
|
|
441
|
+
time you run Harmony after more than a day without the configuration being
|
|
442
|
+
synced.
|
|
316
443
|
|
|
317
444
|
## `version`
|
|
318
445
|
Print Harmony's version.
|