)]}'
{
  "commit": "d9736b2e9a7f30690934e36c03cc2ed580b8bbbe",
  "tree": "ae0670bd5ecb0c1840d1d806694cbdb5c87ac23d",
  "parents": [
    "5f64d496c1da4a610c9feb8a0d19869b701d2b04"
  ],
  "author": {
    "name": "Ignas Anikevicius",
    "email": "240938+aignas@users.noreply.github.com",
    "time": "Sun Nov 08 20:57:35 2026 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Nov 08 20:57:35 2026 +0000"
  },
  "message": "docs(gazelle): document the python_resolve_sibling_imports directive (#4437)\n\nDocument the `python_resolve_sibling_imports` gazelle directive, which\nonly had\na \"Detailed docs are not yet written\" placeholder.\n\nSince 1.6.0 (#3106) gazelle does not resolve absolute imports to sibling\nmodules by default, so e.g. `from typing import TYPE_CHECKING` next to a\n`typing.py` file resolves to the standard library. The docs explain this\ndefault, how to depend on the sibling module with a relative import, and\nhow\nto restore the previous behavior with\n`# gazelle:python_resolve_sibling_imports true`.\n\nThe README of the `sibling_imports` test case claimed that resolving\nsibling\nimports is the default, which is fixed as well.\n\nFixes #3097",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5d3ddf7c13a53ad058ab432be7f4d94eafa3a77a",
      "old_mode": 33188,
      "old_path": "gazelle/docs/directives.md",
      "new_id": "949a8e551d423305dfc09252773667190fa85245",
      "new_mode": 33188,
      "new_path": "gazelle/docs/directives.md"
    },
    {
      "type": "modify",
      "old_id": "d21a671b1c93086bdc13dfc2b3e2ea6ba6bc9313",
      "old_mode": 33188,
      "old_path": "gazelle/python/testdata/sibling_imports/README.md",
      "new_id": "68a4d624ad83b8b2398d0e0b2305f6bdcff20ece",
      "new_mode": 33188,
      "new_path": "gazelle/python/testdata/sibling_imports/README.md"
    }
  ]
}