GitHub Integration for Project

It adds a Development section to the Odoo task form with a Create Branch button. You choose a repository, confirm the branch name, and the branch is created on GitHub and listed on the task with a link. The point is that the developer branches from the task they are already reading, instead of switching tools and inventing a name.

No, and that is the main reason to use this rather than sharing a credential. The access token is stored on the repository record and is readable only by a Git Administrator. A Git User can create branches all day and can never read the token, because the module reads it internally after checking the user's rights.

A fine-grained personal access token with Contents set to Read and write on the repositories you want to use. Metadata read-only is added automatically by GitHub and is required. Nothing else needs enabling.

Only a repository whose Projects list contains that task's project. That list is the authorization boundary, not a convenience filter, so it is re-checked on the server when the button is pressed rather than trusted from the form.

It is caught locally before any request is sent to GitHub, and you get a clear message naming the branch. That ordering matters: it avoids creating a branch remotely and then failing to record it locally.

No. A link is a snapshot taken when the branch was created. This version does not listen for changes on GitHub, so a branch that is later renamed, merged or deleted leaves the recorded name and link as they were.

Yes. Repositories carry a company and are filtered by multi-company record rules, so one company cannot read another company's repositories or its access token.

Use the version selector at the top of this page to pick your Odoo release. Each supported version is published as its own listing and builds on the standard Project app.