@mattpolzin/harmony 5.8.0 → 6.0.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 +11 -3
- package/harmony +2557 -1975
- package/man/harmony.1 +9 -3
- package/package.json +2 -3
package/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
% harmony(1) Version
|
|
1
|
+
% harmony(1) Version 6.0.0 | Harmony User's Guide
|
|
2
2
|
|
|
3
3
|
# NAME
|
|
4
4
|
Harmony - Harmonize with coworkers around GitHub reviewing
|
|
@@ -48,6 +48,13 @@ particular release will build against.
|
|
|
48
48
|
Alternatively, you can build Harmony with Docker (see
|
|
49
49
|
[Docker Build](#docker-build)).
|
|
50
50
|
|
|
51
|
+
### Testing
|
|
52
|
+
Tests can be run with `make test`. You'll need a few common tools in your `PATH`
|
|
53
|
+
to run all the tests:
|
|
54
|
+
- `realpath`
|
|
55
|
+
- `sed`
|
|
56
|
+
- `xargs`
|
|
57
|
+
|
|
51
58
|
## Installation
|
|
52
59
|
For any installation, you need to have a GitHub
|
|
53
60
|
[Personal Access Token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
|
@@ -312,12 +319,13 @@ organization.
|
|
|
312
319
|
|
|
313
320
|
Running `harmony list <team>` will list the members of the given GitHub Team.
|
|
314
321
|
|
|
315
|
-
## `pr [--draft] [-i/--into {<branch-name>}] [#label, ...]`
|
|
322
|
+
## `pr [--draft | --ready] [-i/--into {<branch-name>}] [#label, ...]`
|
|
316
323
|
With a branch checked out will reach out to GitHub to determine if there is an
|
|
317
324
|
open PR for that branch. If there is a PR, Harmony will print a URI that can be
|
|
318
325
|
used to view the PR. If there is not a PR, Harmony will help you create one. New
|
|
319
326
|
and existing PRs can be marked as drafts by specifying the `--draft` flag with
|
|
320
|
-
the `pr` command
|
|
327
|
+
the `pr` command or they can be marked as ready for review with the `--ready`
|
|
328
|
+
flag. The default behavior for new PRs is to mark them ready.
|
|
321
329
|
|
|
322
330
|
If you need to create a PR still, you will be prompted for a branch to open the
|
|
323
331
|
PR against (merge into, eventually), a title for the PR, and a description for
|