)]}'
{
  "commit": "f4f38bec4453564dad0adffbbd99140b37b6e0e3",
  "tree": "bbb0dc7c3ca70e2bec2faf63a98cad7ed99e5889",
  "parents": [
    "e9703ccd8460b5498bec9ee1119cd53ab8f697aa"
  ],
  "author": {
    "name": "Anas Nashif",
    "email": "anas.nashif@intel.com",
    "time": "Tue Jun 10 16:03:06 2025 -0400"
  },
  "committer": {
    "name": "Henrik Brix Andersen",
    "email": "henrik@brixandersen.dk",
    "time": "Fri Jun 12 10:06:34 2026 +0200"
  },
  "message": "ci: add coding guideline scan workflow\n\nAdd initial workflow for scanning the code base using ECLAIR.\nThis is the initial step used for integration, at the moment we only\nbuild one single application using west and enable all zephyr coding\nguidelines covered by the tool.\n\nThis workflow will only run on push events only and will generate a\nSARIF file with all violations that can be downloaded and evaluated\nlocally to help triage and fix issues.\n\nGoal it to address some of the rules with large number of violations\nfirst, get to a manageable number of violations and start posting those\ninto GH dedicated tracking backend.\nLater on we will also start running this on pull requests and flag\nviolations introduced in PRs.\n\nThis should over time also obsolete this existing workflow:\n\n.github/workflows/coding_guidelines.yml\n\nSigned-off-by: Anas Nashif \u003canas.nashif@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "451f12505b855ecc27215bcffca9a8c59dcecf8e",
      "new_mode": 33188,
      "new_path": ".github/workflows/coding_guidelines_full.yml"
    }
  ]
}