)]}'
{
  "commit": "c8be114e77a335fe94c453cd04c37a352aba0028",
  "tree": "a89553ea6bd5362d873edb69e19a71345c09e5df",
  "parents": [
    "db054684a67956c5b86101dd70018accf284be2f"
  ],
  "author": {
    "name": "Christopher Haster",
    "email": "chaster@utexas.edu",
    "time": "Sun Aug 04 16:19:58 2019 -0500"
  },
  "committer": {
    "name": "Christopher Haster",
    "email": "chaster@utexas.edu",
    "time": "Tue Aug 06 21:03:43 2019 -0500"
  },
  "message": "Changed CI to create release note for patches\n\nThis is a result of feedback that the current release notes made it too\ndifficult to see what changes happened on patch releases. From my\nexperience as well it became difficult to chase down which release a\ncommit landed on.\n\nThe risk is that this creates additional noise, both for the release\npage and for user notifications. I am open to feedback if this causes a\nproblem.\n\nOther tweaks on the CI side, these came from iteration with the same\nscheme for coru and equeue:\n\n- Changed version branch updates to be atomic (vN and vN-prefix). This\n  makes it a bit easier to fix if one of the pushes fails due to a rogue\n  branch with the same name.\n\n- Added GEKY_BOT_DRAFT as a CI macro that can optionally switch between\n  only creating drafts or immediately posting a release. The default is\n  what I will be trying with littlefs which is to draft minor/major\n  releases, but automatically create patch release.\n\n  The real benefit of automatic releases is to use on tiny repos that\n  don\u0027t really have an active maintainer. Though this is definitely no\n  longer the case with littlefs, and I\u0027m happy it has gained this much\n  attention.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c7a9bfbacbc41df944aed009afa12b1f884065b7",
      "old_mode": 33188,
      "old_path": ".travis.yml",
      "new_id": "880c861fc76be0b5eb7250121b94ce127d9ee929",
      "new_mode": 33188,
      "new_path": ".travis.yml"
    }
  ]
}