)]}'
{
  "commit": "afb925b446e4f13a05a36f1d87e6b8a1f5a2e27a",
  "tree": "f0b4cd6185a5d55273b33d0d5952db35204a86f7",
  "parents": [
    "94695969085cb2df182f58ee06443c5d7cf233ec"
  ],
  "author": {
    "name": "Leopold",
    "email": "leo@monogon.tech",
    "time": "Sun Jan 08 16:57:28 2023 +0100"
  },
  "committer": {
    "name": "Leopold Schabel",
    "email": "leo@monogon.tech",
    "time": "Mon Jan 16 12:37:40 2023 +0000"
  },
  "message": ".bazelrc: remove hardcoded resource constraints\n\nLet Bazel figure out the appropriate number of jobs and RAM by itself.\nThis should improve default build performance on large machines.\n\nOne possible caveat: we use genrules that consume excessive CPU\non their own (i.e. edk2, kernel...), and removing the jobs limit\nmight cause worse resource contention in some scenarios - but\nfrom limited testing, this does not appear to be a problem.\n\nChange-Id: Ib96d7953b6530fe202f8b7b0aa160cc7e2f2c35c\nReviewed-on: https://review.monogon.dev/c/monogon/+/1070\nTested-by: Jenkins CI\nReviewed-by: Serge Bazanski \u003cserge@monogon.tech\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "710fcf68f0f8addb04ad3004c95b69efb091a628",
      "old_mode": 33188,
      "old_path": ".bazelrc",
      "new_id": "a16469c5ebf27d4c530fee4adeb951422f67c603",
      "new_mode": 33188,
      "new_path": ".bazelrc"
    }
  ]
}