> ## Documentation Index
> Fetch the complete documentation index at: https://docs.codecobra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and deploy

> Merge your changes to staging and production, or download them as a ZIP.

Once CodeCobra finishes building your customization, it's time to review the final result and deploy it to your environment.

## Final review in the live preview

Before deploying, do a thorough test in the live Odoo preview:

* **Walk through the entire workflow** — don't just check that the feature exists, test the full user journey from start to finish
* **Enter realistic data** — use real-world values and scenarios, not just test data
* **Switch between users** — verify that permissions and access rights work correctly for different roles
* **Test edge cases** — what happens with empty fields, zero values, very long text, or unusual inputs?
* **Check existing functionality** — make sure your changes haven't affected other parts of Odoo that should still work normally

<Tip>Ask a colleague to test in the preview too. A fresh pair of eyes often catches things you might miss.</Tip>

## The branch manager

The **Branch Manager** is your deployment control panel. Open it from the task workspace to see:

* All branches created for your task across each connected repository
* Pull request links for each repository
* Merge status and available actions

## Deployment workflow

<Steps>
  <Step title="Merge to staging">
    Click **Merge to Staging** in the Branch Manager. This:

    1. Creates pull requests in your connected GitHub repositories
    2. Merges your task's feature branches into the staging branches
    3. Handles any merge conflicts automatically

    Once merged, deploy the staging branch to your staging environment and test the changes there. This gives you a chance to verify the customization in a more realistic setting alongside your other modules and data.
  </Step>

  <Step title="Test on staging">
    Take time to test the changes on your staging Odoo instance:

    * Verify the customization works with your actual data
    * Test interactions with other installed modules
    * Have team members try the new features
    * Check that reports and exports work correctly
  </Step>

  <Step title="Merge to production">
    Once you're confident everything works on staging, click **Merge to Production** in the Branch Manager. This promotes the changes from your staging branch to your production branch.

    The task moves to the **Complete** stage.
  </Step>
</Steps>

<Warning>Make sure you've thoroughly tested on staging before merging to production. Production merges deploy code that your live users will interact with. Take extra time to verify everything works as expected.</Warning>

## Download as ZIP

If you prefer to deploy manually, or want to keep a backup of the code:

1. Open the Branch Manager
2. Click **Download ZIP**
3. The download includes all custom addons created for the task

This is useful when:

* You deploy Odoo without GitHub integration
* You want to review the code locally before deploying
* You need to share the module files with someone outside CodeCobra
* You want a backup of the module independent of your repository

## Team permissions

If your project belongs to an organization, merge permissions are controlled by team settings:

| Action                  | Who can do it                                                             |
| ----------------------- | ------------------------------------------------------------------------- |
| **Merge to staging**    | Team members with staging merge permission, plus all admins and owners    |
| **Merge to production** | Team members with production merge permission, plus all admins and owners |

If you don't see the merge buttons, check with your organization admin to make sure your team has the appropriate permissions. See [Teams](/organizations/teams) for details on configuring team permissions.

## After deployment

Once your task is complete:

* **Create follow-up tasks** — if you need additional changes or improvements, create a new task in the same project
* **Monitor for issues** — keep an eye on how users interact with the new features
* **Document for your team** — let your team know about the new functionality and how to use it

<CardGroup cols={2}>
  <Card title="Create another task" icon="plus" href="/tasks/create-task">
    Start a new customization or explore more Odoo features.
  </Card>

  <Card title="Manage your team" icon="users" href="/organizations/teams">
    Configure who can merge to staging and production.
  </Card>
</CardGroup>