)]}'
{
  "commit": "4c50deea28badb7007fa6b78c187de50eacdd07a",
  "tree": "d51d267854493562a0b8a5a6480050319a78a39b",
  "parents": [
    "d63060fc9546e2132d0ad7791beb795906372e86"
  ],
  "author": {
    "name": "Daniel Sandler",
    "email": "dsandler@menace.cam.corp.google.com",
    "time": "Tue Mar 02 15:38:03 2010 -0500"
  },
  "committer": {
    "name": "Daniel Sandler",
    "email": "dsandler@android.com",
    "time": "Thu Mar 04 11:56:38 2010 -0500"
  },
  "message": "Fail sync when encountering \"N commits behind.\"\n\nThis is almost always something the user needs to address\nbefore continuing work, so promoting it to a failure (rather\nthan simply an informational message) seems the right way to\ngo. As a side-effect, repo will now exit with a non-zero\nstatus code in this situation, so pipelines of the form\n`repo sync \u0026\u0026 make` will fail if there are branches that\nare stalled due to uploaded but unmerged patches.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "902a2b4484deffb5e4bad3d7be8e418c9ed9f122",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "3d1783f872ba27df1c230ae63e107a0b52cfb5e8",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}