Customer Portal docs
Git delivery

Git delivery: new versions arrive in your repository

2 min read Odoo 20.0

If your Odoo runs from a Git repository (Odoo.sh, your own server with a deployment pipeline, a hosting partner), you do not have to download and copy our modules by hand. With the Git delivery subscription, every new version of the products you choose arrives in your repository by itself.

How it works

  • We write to one branch of our own in your repository: mit-delivery/, your Odoo version and the day the delivery was set up, for example mit-delivery/19.0-2026-11-05.
  • That branch starts from your own default branch, usually main. Your branches are never changed: when you want the new version, you open a merge request from mit-delivery/19.0-2026-11-05 into your branch, review it and merge it. The merge request shows only our modules, our delivery notes and, at the end of your root requirements.txt, a marked block with the Python libraries the modules need: Odoo.sh installs libraries from that file only. Your own lines in it are left as they are.
  • The modules land in the folder you choose, for example addons/metzler, one folder per module, next to your own modules if you like.
  • Each delivery also gets a dated tag, so you can go back to an earlier state. If your Git host refuses tags, the delivery still arrives.
  • Every commit is signed Metzler IT Delivery <[email protected]>. On GitHub it shows as our account MIT-DE, so you always see which changes came from us.
  • After each delivery the person who set it up receives a short e-mail: what arrived and what to do next.
  • New versions arrive within the hour after we publish them.

What your repository looks like

Example after the first delivery to Nordwind Logistik (an example company) with MailDesk Basic, MailDesk Pro and the License Locker:

main                          your branch, unchanged
mit-delivery/19.0-2026-11-05   ours: your main plus one commit per product
  addons/metzler/
    maildesk_mail_client/
    maildesk_mail_client_pro/
    mit_lycense_locker/
    .mit-delivery/            our delivery notes: which files belong to which product
  requirements.txt            your lines, plus our marked block of Python libraries

git log mit-delivery/19.0-2026-11-05
  2037d91 Metzler IT Delivery: MIT License Locker 19.0.1.5.1 (mit_lycense_locker) for Odoo 19.0
  b9007ee Metzler IT Delivery: MailDesk Pro 19.0.4.9.2 (maildesk_mail_client_pro) for Odoo 19.0
  a5198b8 Metzler IT Delivery: MailDesk Basic 19.0.4.9.2 (maildesk_mail_client) for Odoo 19.0
  8b9eaeb Nordwind IT: Nordwind: our Odoo 19 addons

tag  mit-delivery/19.0-2026-11-05/2026-11-05-014353

The e-mail after a delivery: products, versions, branch, tag, folder and the next step

What you need

  • A repository on GitLab.com, GitHub.com or Bitbucket.org. For a Git server of your own, write to [email protected].
  • The Git delivery subscription in the shop. The order shows the price and the term before you pay. One subscription covers your whole company.
  • Permission in your Git host to add a deploy key to the repository, or on GitHub to add our account MIT-DE as a collaborator. Either way you do not share a password.
Delivery follows payment. If the Git delivery invoice stays unpaid, deliveries pause; once it is paid they continue by themselves. See When a payment is late.

Ready? Follow Set up Git delivery step by step.