@mattpolzin/harmony 5.5.1 → 5.7.0

package/man/harmony.1

@@ -1,6 +1,6 @@
 .\" Automatically generated by Pandoc 3.7.0.2
 .\"
-.TH "harmony" "1" "" "Version 5.5.1" "Harmony User\(cqs Guide"
+.TH "harmony" "1" "" "Version 5.7.0" "Harmony User\(cqs Guide"
 .SH NAME
 Harmony \- Harmonize with coworkers around GitHub reviewing
 .SH SYNOPSIS
@@ -380,7 +380,7 @@ configured GitHub organization.
 .PP
 Running \f[CR]harmony list <team>\f[R] will list the members of the
 given GitHub Team.
-.SS \f[CR]pr [\-\-draft] [#label, ...]\f[R]
+.SS \f[CR]pr [\-\-draft] [\-i/\-\-into {<branch\-name>}] [#label, ...]\f[R]
 With a branch checked out will reach out to GitHub to determine if there
 is an open PR for that branch.
 If there is a PR, Harmony will print a URI that can be used to view the
@@ -401,6 +401,15 @@ If you do not have an \f[CR]EDITOR\f[R] environment variable set, you
 will still be able to enter a description from the command line but PR
 templates are only supported when an \f[CR]EDITOR\f[R] is specified.
 .PP
+If you are creating a new PR from a branch that refers to a GitHub issue
+(and you have GitHub branch parsing enabled in your harmony config) then
+harmony will prepend the issue information onto your new PR description
+in a commented out block for you to reference or copy into the PR
+description as needed.
+.PP
+You can specify the branch to merge into via the \f[CR]\-\-into\f[R] CLI
+argument if you want to as an alternative to the interactive prompt.
+.PP
 You can also specify any number of labels to apply by prefixing them
 with `#'.
 For example, \f[CR]harmony pr #backport #bugfix\f[R] would create a PR
@@ -428,12 +437,23 @@ Create a PR for the current branch and add the \f[CR]urgent\f[R] label:
 .EX
 harmony pr #urgent
 .EE
-.SS \f[CR]quick\f[R]
+.PP
+Create a pull request that will merge into the hypothetical
+pre\-existing \f[CR]release/2_0\f[R] branch:
+.IP
+.EX
+harmony pr \-\-into release/2_0
+.EE
+.SS \f[CR]quick [\-\-bugfix]\f[R]
 Helps you create a new GitHub issue and a branch to work on that issue
 all in one go.
 The branch name will be structured such that if you have GitHub branch
 parsing on then the PR you create for the branch later on will refer to
 the issue created now.
+.PP
+By default the branch created will be prefixed with \f[CR]feature\f[R]
+but if you specify the \f[CR]\-\-bugfix\f[R] flag then the branch\(cqs
+prefix will be \f[CR]bugfix\f[R].
 .SS \f[CR]reflect\f[R]
 Show a summary of your review requests and authored pull requests.
 .SS \f[CR]request {team\-slug | +user\-login} [options]\f[R]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mattpolzin/harmony",
-  "version": "5.5.1",
+  "version": "5.7.0",
   "engines": {
     "node": ">=18.0.0"
   },