)]}'
{
  "commit": "eff585190aca2ba62872eae3623667fda95f4d36",
  "tree": "de55c7cf573b5feece4d04bfc8c3c46cb477c8af",
  "parents": [
    "dab5817bcf2b0f9db645bbba5cc6f9c71e9c0e38",
    "f55bea7c2fd1a91106ed8458aa5d4e1054cbeed9"
  ],
  "author": {
    "name": "bors[bot]",
    "email": "26634292+bors[bot]@users.noreply.github.com",
    "time": "Tue Feb 09 18:26:22 2021 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Feb 09 18:26:22 2021 +0000"
  },
  "message": "Merge #271\n\n271: Allow warnings during local development r\u003dalistair23 a\u003djrvanwhy\n\nThis keep\u0027s CI\u0027s behavior where it errors if libtock-rs has warnings.\r\n\r\nThis is a second attempt at PR #270. We can\u0027t specify `RUSTFLAGS` directly because doing so overrides all `rustflags` configurations in `.cargo/config`. Those `rustflags` configs are important because they configure relocation and set the linker script. Instead, I append the `\"deny warnings\"` config to `.cargo/config` in CI itself.\r\n\r\nI tested this by opening two PRs in my fork: [one to test that this PR still builds](https://github.com/jrvanwhy/libtock-rs/pull/15), and [one to test it fails if a warning is present](https://github.com/jrvanwhy/libtock-rs/pull/13).\r\n\r\nI am not terribly happy with this solution (feels really hacky rather than kinda hacky), so any alternative implementation ideas would be appreciated!\n\nCo-authored-by: Johnathan Van Why \u003cjrvanwhy@google.com\u003e\n",
  "tree_diff": []
}