@mattpolzin/harmony 5.6.0 → 5.8.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.
Files changed (4) hide show
  1. package/README.md +26 -7
  2. package/harmony +850 -720
  3. package/man/harmony.1 +38 -8
  4. package/package.json +1 -1
package/man/harmony.1 CHANGED
@@ -1,6 +1,6 @@
1
1
  .\" Automatically generated by Pandoc 3.7.0.2
2
2
  .\"
3
- .TH "harmony" "1" "" "Version 5.6.0" "Harmony User\(cqs Guide"
3
+ .TH "harmony" "1" "" "Version 5.8.0" "Harmony User\(cqs Guide"
4
4
  .SH NAME
5
5
  Harmony \- Harmonize with coworkers around GitHub reviewing
6
6
  .SH SYNOPSIS
@@ -12,7 +12,7 @@ Harmony \- Harmonize with coworkers around GitHub reviewing
12
12
  .PD 0
13
13
  .P
14
14
  .PD
15
- \f[CR]harmony contribute [options] {uri | pr\-number}\f[R]
15
+ \f[CR]harmony contribute [options]\f[R]
16
16
  .PD 0
17
17
  .P
18
18
  .PD
@@ -40,7 +40,7 @@ Harmony \- Harmonize with coworkers around GitHub reviewing
40
40
  .PD 0
41
41
  .P
42
42
  .PD
43
- \f[CR]harmony quick\f[R]
43
+ \f[CR]harmony quick [options]\f[R]
44
44
  .PD 0
45
45
  .P
46
46
  .PD
@@ -258,11 +258,19 @@ Not all configuration properties can be read/set with this command.
258
258
  .SS Properties
259
259
  .TP
260
260
  \f[CR]requestTeams\f[R] (\f[CR]true\f[R]/\f[CR]false\f[R])
261
- When picking a reviewer from a team, request the team as a reviewer as
262
- well.
261
+ When picking a team to review, request review from the whole team, not
262
+ just one user on the team.
263
+ If you have GitHub configured to pick a member of a team to review when
264
+ the team is requested, you probably want to set this to \f[CR]true\f[R]
265
+ so harmony tells GitHub the team from which GitHub should then pick an
266
+ individual.
263
267
  .TP
264
268
  \f[CR]requestUsers\f[R] (\f[CR]true\f[R]/\f[CR]false\f[R])
265
- When requesting a team as a reviewer, pick a user to review as well.
269
+ When requesting a team to review, pick a user from the team to review as
270
+ well.
271
+ If you have GitHub configured to pick a member of a team to review when
272
+ the team is requested, you probably want to set this to \f[CR]false\f[R]
273
+ so harmony does not also pick a user.
266
274
  .TP
267
275
  \f[CR]commentOnRequest\f[R] (\f[CR]none\f[R]/\f[CR]name\f[R]/\f[CR]at\-mention\f[R])
268
276
  When requesting a reviewer chosen by Harmony, comment on the pull
@@ -380,7 +388,7 @@ configured GitHub organization.
380
388
  .PP
381
389
  Running \f[CR]harmony list <team>\f[R] will list the members of the
382
390
  given GitHub Team.
383
- .SS \f[CR]pr [\-\-draft] [#label, ...]\f[R]
391
+ .SS \f[CR]pr [\-\-draft] [\-i/\-\-into {<branch\-name>}] [#label, ...]\f[R]
384
392
  With a branch checked out will reach out to GitHub to determine if there
385
393
  is an open PR for that branch.
386
394
  If there is a PR, Harmony will print a URI that can be used to view the
@@ -401,6 +409,15 @@ If you do not have an \f[CR]EDITOR\f[R] environment variable set, you
401
409
  will still be able to enter a description from the command line but PR
402
410
  templates are only supported when an \f[CR]EDITOR\f[R] is specified.
403
411
  .PP
412
+ If you are creating a new PR from a branch that refers to a GitHub issue
413
+ (and you have GitHub branch parsing enabled in your harmony config) then
414
+ harmony will prepend the issue information onto your new PR description
415
+ in a commented out block for you to reference or copy into the PR
416
+ description as needed.
417
+ .PP
418
+ You can specify the branch to merge into via the \f[CR]\-\-into\f[R] CLI
419
+ argument if you want to as an alternative to the interactive prompt.
420
+ .PP
404
421
  You can also specify any number of labels to apply by prefixing them
405
422
  with `#'.
406
423
  For example, \f[CR]harmony pr #backport #bugfix\f[R] would create a PR
@@ -428,7 +445,14 @@ Create a PR for the current branch and add the \f[CR]urgent\f[R] label:
428
445
  .EX
429
446
  harmony pr #urgent
430
447
  .EE
431
- .SS \f[CR]quick [\-\-bugfix]\f[R]
448
+ .PP
449
+ Create a pull request that will merge into the hypothetical
450
+ pre\-existing \f[CR]release/2_0\f[R] branch:
451
+ .IP
452
+ .EX
453
+ harmony pr \-\-into release/2_0
454
+ .EE
455
+ .SS \f[CR]quick [\-\-bugfix] [issue\-title] [...]\f[R]
432
456
  Helps you create a new GitHub issue and a branch to work on that issue
433
457
  all in one go.
434
458
  The branch name will be structured such that if you have GitHub branch
@@ -438,6 +462,12 @@ the issue created now.
438
462
  By default the branch created will be prefixed with \f[CR]feature\f[R]
439
463
  but if you specify the \f[CR]\-\-bugfix\f[R] flag then the branch\(cqs
440
464
  prefix will be \f[CR]bugfix\f[R].
465
+ .PP
466
+ Any additional arguments other than \f[CR]\-\-bugfix\f[R] will be used
467
+ as the issue\(cqs title.
468
+ If you don\(cqt specify the title as additional arguments, you will be
469
+ prompted for one interactively.
470
+ You will also be prompted for an issue description.
441
471
  .SS \f[CR]reflect\f[R]
442
472
  Show a summary of your review requests and authored pull requests.
443
473
  .SS \f[CR]request {team\-slug | +user\-login} [options]\f[R]
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mattpolzin/harmony",
3
- "version": "5.6.0",
3
+ "version": "5.8.0",
4
4
  "engines": {
5
5
  "node": ">=18.0.0"
6
6
  },