v 16.0 Third Party
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 5405
Technical Name to_git_odoo_version
LicenseOPL-1
Websitehttps://viindoo.com/apps/app/16.0/to_git_odoo_version
Versions 16.0 14.0 11.0 12.0 13.0 15.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 5405
Technical Name to_git_odoo_version
LicenseOPL-1
Websitehttps://viindoo.com/apps/app/16.0/to_git_odoo_version
Versions 16.0 14.0 11.0 12.0 13.0 15.0

What it does

  • By default, developers will have to manually update and connect Git branches to the corresponding Odoo version, which takes a lot of time and effort.
  • This module automatically maps an existing git branch with an existing Odoo version for identification purposes.

Key Features

  • Automatically map existing Git Branches with the corresponding Odoo version.
  • Add extra information on the git branch view.

Supported Editions

  1. Community Edition
  2. Enterprise Edition

Installation

  1. Navigate to Apps.
  2. Search with keyword to_git_odoo_version.
  3. Press Install.

Instructions

After installing the module, navigate to Git > Git > Git Repository and select the repository that you have created. From here, the new fields to indicate whether this git repository belongs to the Odoo Enterprise version or not, and also the default license version applied to this module is added.

Git repository on Viindoo

Navigate to Git > Git > Git Branches, and select the checked-out git branch. On the selected branch, the software will add the following information:

  • Odoo Version: When you pull code from the repository and checkout a version of this branch, the respective Odoo version will be automatically recognized. In case there is an error while pulling code or checkout a branch, press Assign Odoo Version to search for the suitable Odoo version for this git branch.
  • The information will be automatically recognized:
    • Is Odoo Source Code;
    • Odoo Addons Inside;
    • Is Odoo Enterprise.
  • Default License Version: The license applied to the source code of this branch.
  • Depending Branches: Git branches that this branch depends on.
Git branches on Viindoo

Note: You need to install the to_git module to pull code to your repository and checkout git branches.

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.