docs: deprecate get-metadata -> git node metadata

Author: gerkai

README.md

@@ -21,13 +21,15 @@ CLI tools for Node.js Core collaborators.
 
 ## Tools
 
-- [`get-metadata`](./docs/get-metadata.md): Retrieving metadata for a Pull Request.
 - [`git-node`](./docs/git-node.md): Custom Git commands for working with Node.js
   core, e.g. landing Pull Requests.
 - [`ncu-config`](./docs/ncu-config.md): Configure variables for node-core-utils
   to use.
 - [`ncu-team`](./docs/ncu-team.md): Listing members of a team, synchronizing
   special blocks in files with the list of members.
+- [`get-metadata`](./docs/get-metadata.md): Retrieving metadata for a Pull Request.
+  **DEPRECATED**: use [`git node metadata`](./docs/git-node.md#git-node-metadata)
+  instead.
 
 ## Usage
 

docs/get-metadata.md

@@ -1,60 +1,4 @@
 # get-metadata
 
-This tool is inspired by Evan Lucas's [node-review](https://github.com/evanlucas/node-review),
-although it is a CLI implemented with the GitHub GraphQL API.
-
-```
-get-metadata <identifier>
-
-Retrieves metadata for a PR and validates them against nodejs/node PR rules
-
-Options:
-  --version         Show version number                                [boolean]
-  --owner, -o       GitHub owner of the PR repository                   [string]
-  --repo, -r        GitHub repository of the PR                         [string]
-  --file, -f        File to write the metadata in                       [string]
-  --check-comments  Check for 'LGTM' in comments                       [boolean]
-  --max-commits     Number of commits to warn              [number] [default: 3]
-  --help, -h        Show help                                          [boolean]
-```
-
-Examples:
-
-```bash
-PRID=12345
-
-# fetch metadata and run checks on nodejs/node/pull/$PRID
-$ get-metadata $PRID
-# is equivalent to
-$ get-metadata https://github.com/nodejs/node/pull/$PRID
-# is equivalent to
-$ get-metadata $PRID -o nodejs -r node
-
-# Or, redirect the metadata to a file while see the checks in stderr
-$ get-metadata $PRID > msg.txt
-
-# Using it to amend commit messages:
-$ get-metadata $PRID -f msg.txt
-$ echo -e "$(git show -s --format=%B)\n\n$(cat msg.txt)" > msg.txt
-$ git commit --amend -F msg.txt
-```
-
-### Git bash for Windows
-If you are using `git bash` and having trouble with output use `winpty get-metadata.cmd $PRID`.
-
-current known issues with git bash:
-- git bash Lacks colors.
-- git bash output duplicates metadata.
-
-### Features
-
-- [x] Generate `PR-URL`
-- [x] Generate `Reviewed-By`
-- [x] Generate `Fixes`
-- [x] Generate `Refs`
-- [x] Check for CI runs
-- [x] Check if committers match authors
-- [x] Check 48-hour wait
-- [x] Check two TSC approval for semver-major
-- [x] Warn new commits after reviews
-- [ ] Check number of files changed (request pre-backport)
+This tool is deprecated and is currently an alias to
+[`git node metadata`](./git-node.md#git-node-metadata)

docs/git-node.md

@@ -87,6 +87,9 @@ Examples:
 
 ### `git node metadata`
 
+This tool is inspired by Evan Lucas's [node-review](https://github.com/evanlucas/node-review),
+although it is a CLI implemented with the GitHub GraphQL API.
+
 ```
 git-node metadata <identifier>
 
@@ -104,16 +107,38 @@ Options:
   --readme          Path to file that contains collaborator contacts              [string]
   --check-comments  Check for 'LGTM' in comments                                 [boolean]
   --max-commits     Number of commits to warn                        [number] [default: 3]
+```
 
 Examples:
-  git node metadata 12344                        Retrieve the metadata of
-                                                 https://github.com/nodejs/node/pull/12344
-                                                 and validate the PR
-  git node metadata                              Retrieve the metadata of
-  https://github.com/nodejs/node/pull/12344      https://github.com/nodejs/node/pull/12344
-                                                 and validate it
-  git node metadata 167 --repo llnode --readme   Retrieve the metadata of
-  ../node/README.md                              https://github.com/nodejs/llnode/pull/167
-                                                 and validate it using the README in
-                                                 ../node/README.md
-```
+
+```bash
+PRID=12345
+
+# fetch metadata and run checks on nodejs/node/pull/$PRID
+$ git node metadata $PRID
+# is equivalent to
+$ git node metadata https://github.com/nodejs/node/pull/$PRID
+# is equivalent to
+$ git node metadata $PRID -o nodejs -r node
+
+# Or, redirect the metadata to a file while see the checks in stderr
+$ git node metadata $PRID > msg.txt
+
+# Using it to amend commit messages:
+$ git node metadata $PRID -f msg.txt
+$ echo -e "$(git show -s --format=%B)\n\n$(cat msg.txt)" > msg.txt
+$ git commit --amend -F msg.txt
+
+# fetch metadata and run checks on https://github.com/nodejs/llnode/pull/167
+# using the contact in ../node/README.md
+git node metadata 167 --repo llnode --readme ../node/README.md
+```
+
+#### Git bash for Windows
+
+If you are using `git bash` and having trouble with output use
+`winpty git-node.cmd metadata $PRID`.
+
+current known issues with git bash:
+- git bash Lacks colors.
+- git bash output duplicates metadata.