website: regenerate command docs

Summary: There are a few alias reductions not incorporated yet.

Reviewed By: bolinfest

Differential Revision: D41306456

fbshipit-source-id: f60aa3b020b7d50c871003d7360b2ea116574190

website/docs/commands/commands-markdown.json

@@ -808,10 +808,7 @@
     "name": "config",
     "aliases": [
       "config",
-      "showconfig",
-      "debugconfig",
-      "conf",
-      "confi"
+      "conf"
     ],
     "doc": "\n**show config settings**\n\nWith no arguments, print names and values of all config items.\n\nWith one argument of the form `section.name`, print just the value\nof that config item.\n\nWith multiple arguments, print names and values of all config\nitems with matching section names.\n\nWith `--user`, edit the user-level config file. With `--system`,\nedit the system-wide config file. With `--local`, edit the\nrepository-level config file. If there are no arguments, spawn\nan editor to edit the config file. If there are arguments in\n`section.name=value` or `section.name value` format, the appropriate\nconfig file will be updated directly without spawning an editor.\n\nWith `--debug`, the source (filename and line number) is printed\nfor each config item.\n\nSee `sl help config` for more information about config files.\n\nReturns 0 on success, 1 if NAME does not exist.\n",
     "args": [
@@ -1534,8 +1531,7 @@
   "log": {
     "name": "log",
     "aliases": [
-      "log",
-      "history"
+      "log"
     ],
     "doc": "\n**show commit history**\n\nPrint the revision history of the specified files or the entire\nproject.\n\nIf no revision range is specified, the default is the current commit\nand all of its ancestors (`::.`).\n\nFile history is shown without following the rename or copy\nhistory of files. To follow file history across renames and\ncopies, use the `-f/-- follow` option. If the `--follow`\noption is used without a filename, only the ancestors or\ndescendants of the starting revision are shown.\n\nBy default, `sl log` prints the commit's hash, non-trivial\nparents, user, date, time, and the single-line summary. When the\n`-v/--verbose` option is used, the list of changed files and\nfull commit message are shown.\n\nWith the `--graph` option, revisions are shown as an ASCII art\ngraph with the most recent commit at the top. The graph nodes\nare depicted as follows: **o** is a commit, **@** is a working\ndirectory parent, **x** is obsolete, and **+** represents a fork\nwhere the commit from the lines below is a parent of the **o**\nmerge on the same line. Paths in the graph are represented with\n**|**, **/** and so forth. **:** in place of a **|** indicates\none or more revisions in a path are omitted.\n\nUse the `-L/--line-range FILE,M:N` option to follow the\nhistory of lines from **M** to **N** in FILE. With the `-p/--\npatch` option, only diff hunks affecting specified line range\nwill be shown. The `-L` option can be specified multiple\ntimes and requires the `--follow` option. Currently, the line\nrange option is not compatible with `--graph` and is an\nexperimental feature.\n\n`sl log --patch` may generate unexpected diff output for merge\ncommits, as it will only compare the merge commit against\nits first parent. Also, only files different from BOTH parents\nwill appear in the **files:** section.\n\nFor performance reasons, `sl log FILE` may omit duplicate changes\nmade on branches and will not show removals or mode changes. To\nsee all such changes, use the `--removed` switch.\n\nThe history resulting from `-L/--line-range` options depends on\ndiff options: for instance, if white-spaces are ignored,\nrespective changes with only white-spaces in specified line range\nwill not be listed.\n\nSome examples:\n\n- commits with full descriptions and file lists:\n\n```\nsl log -v\n```\n\n- commits ancestral to the working directory:\n\n```\nsl log -f\n```\n\n- last 10 commits on the current branch:\n\n```\nsl log -l 10 -b .\n```\n\n- commits showing all modifications of a file, including removals:\n\n```\nsl log --removed file.c\n```\n\n- all commits that touch a directory, with diffs, excluding merges:\n\n```\nsl log -Mp lib/\n```\n\n- all revision numbers that match a keyword:\n\n```\nsl log -k bug --template \"{rev}\\n\"\n```\n\n- the full hash identifier of the working directory parent:\n\n```\nsl log -r . --template \"{node}\\n\"\n```\n\n- list available log templates:\n\n```\nsl log -T list\n```\n\n- check if a given commit is included in a bookmarked release:\n\n```\nsl log -r \"a21ccf and ancestor(release_1.9)\"\n```\n\n- find all commits by some user in a date range:\n\n```\nsl log -k alice -d \"may 2008 to jul 2008\"\n```\n\n- commits touching lines 13 to 23 for file.c:\n\n```\nsl log -L file.c,13:23\n```\n\n- commits touching lines 13 to 23 for file.c and lines 2 to 6 of  main.c with patch:\n\n```\nsl log -L file.c,13:23 -L main.c,2:6 -p\n```\n\nSee `sl help dates` for a list of formats valid for `-d/--date`.\n\nSee `sl help revisions` for more about specifying and ordering\nrevisions.\n\nSee `sl help templates` for more about pre-packaged styles and\nspecifying custom templates. The default template used by the log\ncommand can be customized via the `ui.logtemplate` configuration\nsetting.\n\nReturns 0 on success.\n",
     "args": [

website/docs/commands/commands.json

@@ -808,10 +808,7 @@
     "name": "config",
     "aliases": [
       "config",
-      "showconfig",
-      "debugconfig",
-      "conf",
-      "confi"
+      "conf"
     ],
     "doc": "show config settings\n\n    With no arguments, print names and values of all config items.\n\n    With one argument of the form ``section.name``, print just the value\n    of that config item.\n\n    With multiple arguments, print names and values of all config\n    items with matching section names.\n\n    With ``--user``, edit the user-level config file. With ``--system``,\n    edit the system-wide config file. With ``--local``, edit the\n    repository-level config file. If there are no arguments, spawn\n    an editor to edit the config file. If there are arguments in\n    ``section.name=value`` or ``section.name value`` format, the appropriate\n    config file will be updated directly without spawning an editor.\n\n    With ``--debug``, the source (filename and line number) is printed\n    for each config item.\n\n    See :prog:`help config` for more information about config files.\n\n    Returns 0 on success, 1 if NAME does not exist.\n\n    ",
     "args": [
@@ -1534,8 +1531,7 @@
   "log": {
     "name": "log",
     "aliases": [
-      "log",
-      "history"
+      "log"
     ],
     "doc": "show commit history\n\n    Print the revision history of the specified files or the entire\n    project.\n\n    If no revision range is specified, the default is the current commit\n    and all of its ancestors (``::.``).\n\n    File history is shown without following the rename or copy\n    history of files. To follow file history across renames and\n    copies, use the ``-f/-- follow`` option. If the ``--follow``\n    option is used without a filename, only the ancestors or\n    descendants of the starting revision are shown.\n\n    By default, :prog:`log` prints the commit's hash, non-trivial\n    parents, user, date, time, and the single-line summary. When the\n    ``-v/--verbose`` option is used, the list of changed files and\n    full commit message are shown.\n\n    With the ``--graph`` option, revisions are shown as an ASCII art\n    graph with the most recent commit at the top. The graph nodes\n    are depicted as follows: **o** is a commit, **@** is a working\n    directory parent, **x** is obsolete, and **+** represents a fork\n    where the commit from the lines below is a parent of the **o**\n    merge on the same line. Paths in the graph are represented with\n    **|**, **/** and so forth. **:** in place of a **|** indicates\n    one or more revisions in a path are omitted.\n\n\n    .. container:: verbose\n\n      Use the ``-L/--line-range FILE,M:N`` option to follow the\n      history of lines from **M** to **N** in FILE. With the ``-p/--\n      patch`` option, only diff hunks affecting specified line range\n      will be shown. The ``-L`` option can be specified multiple\n      times and requires the ``--follow`` option. Currently, the line\n      range option is not compatible with ``--graph`` and is an\n      experimental feature.\n\n    .. note::\n\n      :prog:`log --patch` may generate unexpected diff output for merge\n      commits, as it will only compare the merge commit against\n      its first parent. Also, only files different from BOTH parents\n      will appear in the **files:** section.\n\n    .. note::\n\n      For performance reasons, :prog:`log FILE` may omit duplicate changes\n      made on branches and will not show removals or mode changes. To\n      see all such changes, use the ``--removed`` switch.\n\n    .. container:: verbose\n\n       .. note::\n\n          The history resulting from ``-L/--line-range`` options depends on\n          diff options: for instance, if white-spaces are ignored,\n          respective changes with only white-spaces in specified line range\n          will not be listed.\n\n    .. container:: verbose\n\n      Some examples:\n\n      - commits with full descriptions and file lists::\n\n          @prog@ log -v\n\n      - commits ancestral to the working directory::\n\n          @prog@ log -f\n\n      - last 10 commits on the current branch::\n\n          @prog@ log -l 10 -b .\n\n      - commits showing all modifications of a file, including removals::\n\n          @prog@ log --removed file.c\n\n      - all commits that touch a directory, with diffs, excluding merges::\n\n          @prog@ log -Mp lib/\n\n      - all revision numbers that match a keyword::\n\n          @prog@ log -k bug --template \"{rev}\\n\"\n\n      - the full hash identifier of the working directory parent::\n\n          @prog@ log -r . --template \"{node}\\n\"\n\n      - list available log templates::\n\n          @prog@ log -T list\n\n      - check if a given commit is included in a bookmarked release::\n\n          @prog@ log -r \"a21ccf and ancestor(release_1.9)\"\n\n      - find all commits by some user in a date range::\n\n          @prog@ log -k alice -d \"may 2008 to jul 2008\"\n\n      - commits touching lines 13 to 23 for file.c::\n\n          @prog@ log -L file.c,13:23\n\n      - commits touching lines 13 to 23 for file.c and lines 2 to 6 of\n        main.c with patch::\n\n          @prog@ log -L file.c,13:23 -L main.c,2:6 -p\n\n    See :prog:`help dates` for a list of formats valid for ``-d/--date``.\n\n    See :prog:`help revisions` for more about specifying and ordering\n    revisions.\n\n    See :prog:`help templates` for more about pre-packaged styles and\n    specifying custom templates. The default template used by the log\n    command can be customized via the ``ui.logtemplate`` configuration\n    setting.\n\n    Returns 0 on success.\n\n    ",
     "args": [

website/docs/commands/config.md

@@ -2,9 +2,9 @@
 sidebar_position: 10
 ---
 
-## config | showconfig | debugconfig | conf | confi
+## config | conf
 <!--
-  @generated SignedSource<<1faee5ba9a142b2c16085a7a3460b0be>>
+  @generated SignedSource<<52f5803ad3fb8f606b2862076e43d59a>>
   Run `./scripts/generate-command-markdown.py` to regenerate.
 -->
 

website/docs/commands/log.md

@@ -2,9 +2,9 @@
 sidebar_position: 23
 ---
 
-## log | history
+## log
 <!--
-  @generated SignedSource<<3c52bbd5296b7747b8082e476b2c7484>>
+  @generated SignedSource<<193144e419e00c8abfb4dcde9485ecb8>>
   Run `./scripts/generate-command-markdown.py` to regenerate.
 -->