Customer Portal docs
Git delivery

Set up Git delivery step by step

4 min read Odoo 20.0

Setting up takes about five minutes. You need the Git delivery subscription and access to your repository's settings.

1. Open Git delivery

On My account, click Git delivery. There is one card for each Odoo version you hold products for.

Git delivery before it is connected: the Odoo 19.0 card, Not connected

2. Say where we should deliver

  1. Repository address (SSH): in your Git host open the repository, click Code or Clone and copy the address under Clone with SSH, for example [email protected]:nordwind-logistik/odoo.git.
  2. Folder in the repository: where our modules go, for example addons/metzler. Leave it empty for the repository root.
  3. Products to deliver: tick the products you want. With all of them ticked you receive everything you hold, including products you buy later. If you tick only some, a product you buy later appears as a new box to tick. Select all and Clear help.
  4. Click Save and create my deploy key.

Where the address is on GitHub: open the repository, click Code (1), choose SSH (2) and copy the address with the copy button (3).

GitHub: Code, then SSH, then copy the address

Paste it into Repository address (SSH) on our page:

The address, the folder and three products ticked

3. Give us write access

There are two ways. Both let us write only to the branch mit-delivery/19.0-2026-11-05 and its dated tags, and you can take the access back any time.

  • Option A: the deploy key, for GitLab, GitHub and Bitbucket. You add a key that works for this one repository only, and you can carry on at once.
  • Option B: our GitHub account MIT-DE, for GitHub only. You invite one user and copy no key. We switch your delivery over by hand, so it starts once we have confirmed it.

Option A: the deploy key

The page now shows a deploy key made for your repository. A deploy key works like a robot user that can write to this one repository only.

The deploy key with Copy key, and the GitLab steps

Click Copy key, then add it in your Git host:

On Odoo.sh? Your code lives on GitHub. Add the key in the GitHub repository your Odoo.sh project is connected to, not in Odoo.sh.

GitLab

  1. Open the project, then Settings → Repository → Deploy keys → Add new key.
  2. Title: Metzler IT delivery. Key: paste the key.
  3. Tick Grant write permissions to this key, then Add key.
  4. If all branches are protected (pattern *), allow pushes to mit-delivery/* under Settings → Repository → Protected branches.

GitHub

  1. Open the repository, then Settings (1) → Deploy keys (2) → Add deploy key.
  2. Title (3): Metzler IT delivery. Key (4): paste the key.
  3. Tick Allow write access (5), then click Add key (6).
  4. If a branch ruleset covers all branches, it must allow mit-delivery/*.

GitHub: Settings, Deploy keys, the title, the key, Allow write access ticked, Add key

Without Allow write access we can read your repository but not deliver to it.

Bitbucket

  1. Bitbucket's repository access keys can only read. Use a separate user for us instead, for example metzler-delivery in your workspace.
  2. Give that user Write permission on the repository (Repository settings → Repository permissions).
  3. Logged in as that user: Personal settings → SSH keys → Add key, and paste the key.

Option B: our GitHub account MIT-DE

If your repository is on GitHub, which includes Odoo.sh, you can invite our account instead of adding a key. You do not need the deploy key the page shows.

  1. Open the repository, then Settings → Collaborators (in an organization: Collaborators and teams) → Add people.
  2. Enter MIT-DE and choose the role Write.
  3. Write to [email protected] with the repository address. We accept the invitation, check that it came from your repository, and switch your delivery to our account. We tell you when it is done.
  4. If a branch ruleset covers all branches, it must allow mit-delivery/*.
Why not on our page? Our account can reach every repository that invited it. So we switch a delivery to it only after checking that the invitation came from your repository; a deploy key proves that by itself.

4. Check and deliver

Back on the Git delivery page, click Check and deliver (with option B, once we have told you the switch is done). We connect and, if it works, queue the first delivery. The page says so, and the card shows Connected.

The check succeeded: the repository answered, the first delivery is queued, the card says Connected

If the check fails, the page says why: usually the address is wrong, or the key or the invitation is missing. The check only reads, so a key without write access, or protected branches that do not allow mit-delivery/*, show up at the first delivery: the card then says why under Last problem. Fix it in your Git host and click Check and deliver again (once a minute at most).

5. Take the new version into your Odoo

After the first delivery: its date, the branch and the folder for addons_path

  1. You receive the delivery e-mail. In your Git host, open a merge request from mit-delivery/19.0-2026-11-05 into your branch, review it and merge it.
  2. Make sure the folder is in your Odoo's addons_path; the page shows the exact folder.
  3. Update the modules in Odoo (Apps → the module → Upgrade), or restart Odoo with -u and the module names.

Later changes

  • Change the folder or the products and click Save changes.
  • Disconnect this repository stops the deliveries and deletes the key on our side. In your Git host, remove the deploy key, or remove MIT-DE from the collaborators.