)]}'
{
  "commit": "203724192f37239c3a2ee35fd6a982ff810aefcc",
  "tree": "0bc75e1a7334186d070112b52a0c590688b9dce5",
  "parents": [
    "95632c8a1e5953eddcb3073764b3db2c7f7bddb5"
  ],
  "author": {
    "name": "Philip Zeyliger",
    "email": "philip@bold.dev",
    "time": "Thu Jun 05 02:12:10 2025 +0000"
  },
  "committer": {
    "name": "Philip Zeyliger",
    "email": "philip@bold.dev",
    "time": "Wed Jun 04 20:35:18 2025 -0700"
  },
  "message": "git_tools: improve commit range selection when fewer than 10 commits exist\n\nReplace hardcoded fromCommit~10 check with flexible loop that tries\noffsets from 10 down to 0, selecting the first valid range.\n\nProblem Analysis:\nThe getGitLog function was failing when repositories had fewer than\n10 commits total. It attempted to check if fromCommit~10 existed and\nfell back to fromCommit..HEAD only if that check failed, causing\nissues in new repositories or shallow clones.\n\nImplementation Changes:\n- Added loop from i\u003d10 down to i\u003d0 to find the largest valid offset\n- Use git rev-parse --verify to test each fromCommit~i combination\n- Fall back to fromCommit..HEAD when no offset works (i\u003d0 case)\n- Maintain same git log command structure and output format\n\nBenefits:\n- Works correctly with repositories of any size\n- Gracefully handles edge cases like single commits\n- Maintains existing functionality for larger repositories\n- No changes to function signature or return format\n\nTesting:\nAll existing tests continue to pass, confirming backward compatibility.\n\nCo-Authored-By: sketch \u003chello@sketch.dev\u003e\nChange-ID: sc8c08e32b68c72dck\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "18a241d9183b579c14e1057b1eebe9bd37509ced",
      "old_mode": 33188,
      "old_path": "git_tools/git_tools.go",
      "new_id": "6dddffb516161070c613bdd87c84c8bd82c4bef7",
      "new_mode": 33188,
      "new_path": "git_tools/git_tools.go"
    }
  ]
}