rush change

usage: rush change [-h] [-v] [-b BRANCH]

Asks a series of questions and then generates a <branchname>-<timstamp>.json
file in the common folder. The `publish` command will consume these files and
perform the proper version bumps. Note these changes will eventually be
published in a changelog.md file in each package. The possible types of
changes are: MAJOR - these are breaking changes that are not backwards
compatible. Examples are: renaming a public class, adding/removing a
non-optional parameter from a public API, or renaming an variable or function
that is exported. MINOR - these are changes that are backwards compatible
(but not forwards compatible). Examples are: adding a new public API or
adding an optional parameter to a public API PATCH - these are changes that
are backwards and forwards compatible. Examples are: Modifying a private API
or fixing a bug in the logic of how an existing API works. HOTFIX
(EXPERIMENTAL) - these are changes that are hotfixes targeting a specific
older version of the package. When a hotfix change is added, other changes
will not be able to increment the version number.Enable this feature by
setting 'hotfixChangeEnabled' in your rush.json.

Optional arguments:
  -h, --help            Show this help message and exit.
  -v, --verify          Verify the change file has been generated and that it
                        is a valid JSON file
  -b BRANCH, --target-branch BRANCH
                        If this parameter is specified, compare current
                        branch with the target branch to get changes. If this
                        parameter is not specified, the current branch is
                        compared against the "master" branch.