> ## Content Index
> Fetch the complete content index at: https://blog.esadax.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Esadax and Git Deployment Overview
- URL: https://blog.esadax.com/en/esadax-and-git-deployment-overview-en-2/
- Published: 2026-11-15T05:16:50.000Z
- Updated: 2026-11-15T05:16:50.000Z
- Author: Esadax 
- Tags: #tr-ci-41-git-git, #en, #mdx-imported, CI

**Esadax and Git Deployment Overview**

1. **Project Setup and Production Branch Selection:**
  - When creating a new project from a Git repository, Esadax automatically selects the production branch based on the presence of main or master branches. If these are absent, it uses the Git repository's default branch setting.
2. **Team Management and Deployment Permissions:**
  - **Hobby Teams:** Only team owners connected via their Git account can deploy commits. This ensures that non-owners cannot push changes unless they become members of a Pro team.
  - **Pro Teams:** Members can deploy after being added, with the commit author's identity checked against the team's Login Connections.
3. **Pull Requests and Authorization:**
  - After forking a public repository, pull requests may require authorization if they modify esadax.json or environment variables. This is a security measure to prevent sensitive information leaks.
  - If the commit author is already a team member, the authorization step is skipped.
4. **Preview Branches and Phases:**
  - **Default Preview:** Changes pushed to non-production branches (e.g., main) are served through preview domains like `url-composition.project-name-branch.esadax.app`.
  - **Multiple Phases (e.g., Staging):** Additional Git branches can be created to assign specific domains and environment variables, allowing for testing before merging into production.
5. **Merging and Branch Management:**
  - After testing in preview phases, changes are merged into the production branch. Preview branches are typically kept active for future use unless deleted.