Import modules git commits data

[sebalix]

What
Import git commits info for each module (sha, message, author, committer, dates, files changed...)

Why

• Get an accurate view of authors/committers, dates
• Ability to compare git commits from one branch to another for a given module (what is actually doing the integration of oca-port in odoo_repository_migration, but it should be faster (PostgreSQL vs git log access), and allowing such comparisons for any migration paths on the fly (even backports).

How
There is jc that can parse git logs to get JSON:

$ git log --format=fuller --stat -- odoo_repository_migration | jc --git-log -p

[
  {
    "commit": "5e9c9c0977c665c9ce40c9dde029d1ce5af9c21c",
    "author": "Sébastien Alix",
    "author_email": "sebastien.alix@camptocamp.com",
    "date": "Sat Jan 17 13:16:12 2026 +0100",
    "commit_by": "Sébastien Alix",
    "commit_by_email": "sebastien.alix@camptocamp.com",
    "commit_by_date": "Sat Jan 17 13:28:43 2026 +0100",
    "stats": {
      "files_changed": 3,
      "insertions": 3,
      "deletions": 3,
      "files": [
        "odoo_repository_migration/README.rst",
        "odoo_repository_migration/__manifest__.py",
        "odoo_repository_migration/static/description/index.html"
      ]
    },
    "message": "Update all modules manifest and README with new repo info",
    "epoch": 1768652172,
    "epoch_utc": null
  },
  [...]
]

Also available as a Python package:

>>> import jc
>>> cmd_output = subprocess.check_output(...)
>>> data = jc.parse('git_log', cmd_output)

Questions
How much space it's about to take in DB? (not sure we need to store the diffs, but still).

cc @sebastienbeau maybe something you are interested in?

[hparfr]

Hi,

I don't see the benefit of doing it here.

Ability to compare git commits from one branch to another for a given module

If the goal is to be sure no commits are lost or counterfeit during a migration, then it should be a check of oca-bot in the PR.

[sebalix]

Not sure if oca-bot will be able to catch everything, especially a module on branch X that continues to get improvements even if already migrated on X+1 to X+4. And backports too. Still, oca-bot could help porting commits yes.

The goal would be to do the computation that oca-port is doing currently, without relying everytime on git log which is very slow (it's the slowest job currently in Odoo MCA).
Another one in the future could be providing really detailed RAG for AI agents (with module code alongside its commits, PRs description and comments) to ease the migration of modules or requesting anything with natural language thanks to https://github.com/pgvector/pgvector extension (by describing a customer need, how to implement it etc), that could help a lot functional people. But it's just ideas ATM.