)]}'
{
  "commit": "5400677903bdb852e0ca89e41e009afb8a1b6239",
  "tree": "44bf20644f96d6270b6bf443202bc19b989cece3",
  "parents": [
    "72ee67319f703201631b33697291720afd4e1d66"
  ],
  "author": {
    "name": "Elijah Newren",
    "email": "newren@gmail.com",
    "time": "Tue Dec 11 08:11:34 2018 -0800"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Dec 28 12:49:48 2018 -0800"
  },
  "message": "t5407: add a test demonstrating how interactive handles --skip differently\n\nThe post-rewrite hook is documented as being invoked by commands that\nrewrite commits such as commit --amend and rebase, and that it will\nbe called for each rewritten commit.\n\nApparently, the three backends handled --skip\u0027ed commits differently:\n  am: treat the skipped commit as though it weren\u0027t rewritten\n  merge: same as \u0027am\u0027 backend\n  interactive: treat skipped commits as having been rewritten to empty\n     (view them as an empty fixup to their parent)\n\nFor now, just add a testcase documenting the different behavior (use\n--keep to force usage of the interactive machinery even though we have\nno empty commits).  A subsequent commit will remove the inconsistency in\n--skip handling.\n\nSigned-off-by: Elijah Newren \u003cnewren@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9b2a274c71f40ace060069212055a29f9a3c4203",
      "old_mode": 33261,
      "old_path": "t/t5407-post-rewrite-hook.sh",
      "new_id": "6426ec89919236c5d798eeb56e06d252119097c5",
      "new_mode": 33261,
      "new_path": "t/t5407-post-rewrite-hook.sh"
    }
  ]
}