| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Project (project)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4176 |
| Technical Name |
github_project_portal |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Project (project)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4176 |
| Technical Name |
github_project_portal |
| License | OPL-1 |
| Website | https://www.ganemo.co |
GitHub Project Portal
Automated GitFlow & Development Lifecycle
Manage your development lifecycle directly from Odoo. Create branches, manage Pull Requests, and deploy releases without leaving your project board.
What We're Solving
----------------
Automated GitFlow
Forget about manual branch creation. Moving a task to "Doing" automatically creates the correct branch (Feature/Fix). Moving to "Review" creates the Pull Request. The entire flow is automated and linked to your Odoo tasks.
Module Validation
Ensure quality and version control. The system validates
that the correct module is being modified and enforces __manifest__.py
updates. No more accidental commits to the wrong module or missing version bumps.
Setup & User Manual
Step-by-Step implementation
1. Configuration
Prepare the system for GitHub integration:
- Configure your GitHub Token in System Parameters.
- Set up your Organization and Repositories in Odoo.
- Enable "GitHub Project" on your Odoo Project tasks.
- Assign specific Review Teams.
2. Operating Manual (Workflow)
Follow the strict GitFlow process:
1. Start Task (DOING)
Move task to DOING. Choose your
repository and module. Odoo creates the branch automatically (e.g.,
FIX_123_MÓDULO).
2. Request Review (REVIEW)
Move task to REVIEW. Odoo creates a Pull Request to the development branch and assigns reviewers. Validation scripts run to check for errors.
3. Test & Validate (TESTING)
Upon approval, move to TESTING. The PR is merged, and a Release Candidate (RC) tag is generated for QA validation.
4. Deploy (PROD)
Move to PROD. The system merges to production, creates the final Release/Tag, and cleans up temporary branches.
Global Ready | Multi-Language Support
This module is fully translated into English and Spanish (en_US, es_ES, es_PE, es_MX), ensuring a professional experience for international organizations.
Why Choose Ganemo?
----------------
Ganemo is the world's leading Odoo App developer and a multi-award-winning Gold Partner. For over 5 years, we have been recognized as the #1 seller of high-quality apps on the Odoo App Store. Trusted as the "Best Partner" in USA, Mexico, Chile, Spain, Colombia, Ecuador, and Peru, we deliver robust, secure, and localization-compliant solutions for global businesses.
Get a Quote & Resolve Commercial Doubts
Join thousands of satisfied clients on Odoo. Contact our sales team directly.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Schedule Meeting
Need More? We Do It All
Professional Odoo Services
ERP Implementation
Transform your business with a full Odoo implementation. We analyze, configure, and train your team to maximize productivity. From Accounting to Inventory, we handle the complexity so you can focus on growth.
Module Dev & Migration
Need a custom feature? Or stuck on an older version? We develop high-performance custom modules and migrate your existing code to Odoo 19 with zero data loss. Expert developers at your service.
QA / User Testing Scenarios
Enterprise Validation Plan
Scenario 1: Branch Creation (Doing)
- Create a task in Odoo and select the repository.
- Move the task to "Doing".
- Check GitHub: A new branch (e.g.,
FIX_...) should be created automatically.
Scenario 2: Pull Request (Review)
- Move the task to "Review".
- A PR is created in GitHub targeting the development branch.
- Reviewers are assigned automatically.
- Validation: If
__manifest__.pyhasn't been updated, the system should raise an error.
Scenario 3: Release to Prod (Testing -> Prod)
Simulate a full release deployment.
- Move to Testing: Merges to Dev branch.
- Move to Prod: Merges to Master/Main and creates Release.
- Validation: Verify the GitHub Release exists and temporary branches are deleted.
FAQ & Troubleshooting
Common Resolutions
Error: "No se encontró modificación en el archivo __manifest__.py"
Reason: You modified files but forgot to update the module version in the manifest.
Fix: Commit
a change to __manifest__.py (increment version) and push again.
Can I skip stages?
Reason: The module enforces a strict GitFlow.
Fix: You must follow the sequence Backlog -> Doing -> Review -> Testing -> Prod. Skipping creates inconsistencies in git branches.
Commercial & Sales
For inquiries about licenses, demos, or partnerships.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Technical Support
Existing customers regarding module functionality.
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