)]}'
{
  "commit": "f9b7683a3bf979d6cef50d691165280d64566ee4",
  "tree": "b9d86c89ebf62c6a81898223f0f702f6c4c5eac6",
  "parents": [
    "7e59de2bcc8513ba28701062be2637d90cb6eeff"
  ],
  "author": {
    "name": "Simon Ruggier",
    "email": "Simon80@gmail.com",
    "time": "Fri Jul 31 17:18:34 2015 -0400"
  },
  "committer": {
    "name": "Simon Ruggier",
    "email": "Simon80@gmail.com",
    "time": "Tue Aug 04 18:41:20 2015 -0400"
  },
  "message": "Include project path in --force-sync error message\n\nFor projects that have been cloned outside of the repo command (or\ncloned a long time ago), commit abaa7f312f1b6c8d11d7c757fe909900ce5788b5\nintroduced an error message to invite the user to use --force-sync.\nHowever, due to the risk of data loss, it\u0027s useful to know which\nproject\u0027s git directory is being replaced before deciding whether or not\nto provide --force-sync.\n\nThis change updates the exception\u0027s associated value to include the\nproject\u0027s relative path and explain to the user how they can resolve the\nissue. A previous version of this commit used the project name. However,\nfor projects that have multiple work trees, the name can be ambiguous,\nwhile the path clearly identifies which git directory will be replaced.\n\nChange-Id: If717e66fda4d19accc0a8e889a91f4cd4ff14dff\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9cb7542e933f3fc0c6c8b3c679be990ad2c9cf0f",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "fb9df2aa414d0a8fa7960ef0022ebe28ec079ae0",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}