@mattpolzin/harmony 6.3.1 → 6.5.0

package/man/harmony.1

@@ -1,6 +1,6 @@
 .\" Automatically generated by Pandoc 3.7.0.2
 .\"
-.TH "harmony" "1" "" "Version 6.3.1" "Harmony User\(cqs Guide"
+.TH "harmony" "1" "" "Version 6.5.0" "Harmony User\(cqs Guide"
 .SH NAME
 Harmony \- Harmonize with coworkers around GitHub reviewing
 .SH SYNOPSIS
@@ -85,17 +85,6 @@ Running Harmony requires NodeJS 18+ (and a local installation of
 If you\(cqd like to try Harmony out without even \(lqinstalling\(rq it
 and you have Nix installed with flakes enabled, you can run it as
 \f[CR]nix run github:mattpolzin/harmony\f[R].
-.SS Build time
-Building the latest commits of Harmony requires a HEAD build of the
-Idris 2 compiler.
-Each release page also indicates the version of Idris 2 that particular
-release will build against.
-.PP
-Alternatively, you can build Harmony with Docker (see Docker Build).
-.SS Testing
-Tests can be run with \f[CR]make test\f[R].
-You\(cqll need a few common tools in your \f[CR]PATH\f[R] to run all the
-tests: \- \f[CR]realpath\f[R] \- \f[CR]sed\f[R] \- \f[CR]xargs\f[R]
 .SS Bash completion
 Set up Bash completion by adding the following to your Bash resource
 file or profile:
@@ -226,6 +215,16 @@ Optionally extract a Jira ticket slug or GitHub issue number from the
 branch name and prepend it to the PR title or body to link the PR and
 ticket/issue.
 .TP
+\f[CR]bugfixPRTitlePrefix\f[R] (optional string)
+A string to prefix default PR titles with when the branch the PR is
+being created from is determined to be a bugfix branch (branch name
+starts with `bugfix').
+For example, a common prefix is `[fix]'.
+.TP
+\f[CR]addPrTreeDescription\f[R] (\f[CR]true\f[R]/\f[CR]false\f[R])
+Determines whether to add a tree of PRs to the description for any PR
+that is into a branch other than the \f[CR]mainBranch\f[R] configured.
+.TP
 \f[CR]defaultRemote\f[R] (optional string)
 When pushing new branches, what remote destination should be used.
 .TP
@@ -333,12 +332,16 @@ 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 | \-\-ready] [\-i/\-\-into {<branch\-name>}] [#label, ...]\f[R]
+.SS \f[CR]pr [\-\-draft | \-\-ready] [\-i/\-\-into {<branch\-name>}] [\-\-print\-tree] [#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
 PR.
 If there is not a PR, Harmony will help you create one.
+The \f[CR]\-\-print\-tree\f[R] flag will print a tree of PRs for
+branches between the current one and the \f[CR]mainBranch\f[R] of the
+repository instead of just printing the URI for the current branch\(cqs
+PR.
 New and existing PRs can be marked as drafts by specifying the
 \f[CR]\-\-draft\f[R] flag with the \f[CR]pr\f[R] command or they can be
 marked as ready for review with the \f[CR]\-\-ready\f[R] flag.

package/package.json

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