diff options
| author | Teddy Wing | 2020-08-23 20:55:08 +0200 |
|---|---|---|
| committer | Teddy Wing | 2020-08-23 20:55:08 +0200 |
| commit | 623f60844478a3cfc60d697f5e5d804254c01c50 (patch) | |
| tree | 981f8e57bc35fbc3022a58f7442a9e7f92926491 /README.md | |
| parent | bce2e554408404233b66f11e2e342d83c3ca81dd (diff) | |
| download | git-suggestion-623f60844478a3cfc60d697f5e5d804254c01c50.tar.bz2 | |
Rename `git-sugpatch` to `git-sugdiff`
The word "patch" reminds me more of the `patch` Unix command, which is
what `git-sugapply` does.
Since this command outputs diffs, it makes more sense to call it
`sugdiff`. That also brings these closer to the native Git commands,
`git-diff` and `git-apply`.
I had chosen "patch" originally because the command generated a unified
diff that could be used as a patch file to apply to the repo.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -15,7 +15,7 @@ copy in a Git repository. $ git checkout 74a39f3 Note: checking out '74a39f3'. … - $ git sugpatch https://github.com/cli/cli/pull/1150#discussion_r438352211 + $ git sugdiff https://github.com/cli/cli/pull/1150#discussion_r438352211 diff --git a/pkg/cmd/api/api.go b/pkg/cmd/api/api.go index b4a8dbd..c081b50 100644 --- a/pkg/cmd/api/api.go |