)]}'
{
  "commit": "a0343f3002d229fd351ac4662ced580164657085",
  "tree": "5faaf672453d2ca8bb1c981e1d6c18628446a513",
  "parents": [
    "c39fffc1c90b174fe4ff40e0ce9f597e3d57778f"
  ],
  "author": {
    "name": "Ævar Arnfjörð Bjarmason",
    "email": "avarab@gmail.com",
    "time": "Thu Oct 13 17:39:28 2022 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Oct 13 09:32:58 2022 -0700"
  },
  "message": "tests: assert consistent whitespace in -h output\n\nAdd a test for the *.txt and *.c output assertions which asserts that\nfor \"-h\" lines that aren\u0027t the \"usage: \" or \" or: \" lines they start\nwith the same amount of whitespace. This ensures that we won\u0027t have\nbuggy output like:\n\n   [...]\n   or: git tag [-n[\u003cnum\u003e]]\n               [...]\n       [--create-reflog] [...]\n\nWhich should instead be like this, i.e. the options lines should be\naligned:\n\n   [...]\n   or: git tag [-n[\u003cnum\u003e]]\n               [...]\n               [--create-reflog] [...]\n\nIt would be better to be able to use \"test_cmp\" here, i.e. to\nconstruct the output we expect, and compare it against the actual\noutput.\n\nFor most built-in commands this would be rather straightforward. In\n\"t0450-txt-doc-vs-help.sh\" we already compute the whitespace that a\n\"git-$builtin\" needs, and strip away \"usage: \" or \" or: \" from the\nstart of lines. The problem is:\n\n * For commands that implement subcommands, such as \"git bundle\", we\n   don\u0027t know whether e.g. \"git bundle create\" is the subcommand\n   \"create\", or the argument \"create\" to \"bundle\" for the purposes of\n   alignment.\n\n   We *do* have that information from the *.txt version, since the\n   part within the \u0027\u0027-quotes should be the command \u0026 subcommand, but\n   that isn\u0027t consistent (e.g. see \"git bundle\" and \"git\n   commit-graph\", only the latter is correct), and parsing that out\n   would be non-trivial.\n\n * If we were to make this stricter we have various\n   non-parse_options() users (e.g. \"git diff-tree\") that don\u0027t have the\n   nicely aligned output which we\u0027ve had since\n   4631cfc20bd (parse-options: properly align continued usage output,\n   2021-09-21).\n\nSo rather than make perfect the enemy of the good let\u0027s assert that\nfor those lines that are indented they should all use the same\nindentation.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason \u003cavarab@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8fd20b6dba6b9592d5f081f823ba35de3efea086",
      "old_mode": 33261,
      "old_path": "t/t0450-txt-doc-vs-help.sh",
      "new_id": "cd3969e852bb06fa3361cd9e8e13d71c5fb514c4",
      "new_mode": 33261,
      "new_path": "t/t0450-txt-doc-vs-help.sh"
    }
  ]
}