> ## 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.

# Production Branch
- URL: https://blog.esadax.com/en/production-branch-2/
- Published: 2026-11-15T05:16:41.000Z
- Updated: 2026-11-15T05:16:41.000Z
- Author: Esadax 
- Tags: #tr-ci-08-projects-06-git-13-production-branch, #en, #mdx-imported, CI

The **Production Branch** determines which branch in your Git repository triggers **Production Deployments** on Esadax.

By default, this is set to the `main` branch — meaning any commit pushed to `main` will automatically trigger a full **Production Deployment**.

---

## Why Set a Production Branch?

- Ensures a **stable and reliable deployment process** for your live environment.
- Keeps production separate from development or staging branches.
- Automatically triggers a production update when the designated branch is updated.

---

## Default Behavior

If you haven’t changed the setting, Esadax treats the `main` branch as the **Production Branch**:

- Pushing to `main` → 🚀 Production Deployment
- Pushing to any other branch → 🧪 Preview Deployment

---

## How to Change the Production Branch

You can override the default behavior by selecting a different branch:

1. Go to your **Project Settings**.
2. Navigate to the **Git** or **Deployments** section.
3. Find the **Production Branch** field.
4. Enter the name of your desired branch (e.g., `release`, `production`, `v1`).

Once saved, future commits to this branch will trigger Production Deployments instead of Preview ones.

---

## Use Cases

- You use a `develop → staging → production` Git flow and want to deploy `production` as the live version.
- Your main development occurs on `main`, but live deployments are controlled through `release`.

---

## Best Practices

- **Protect your Production Branch** in your Git provider to avoid accidental changes.
- Use **pull requests or merge requests** to promote code into your Production Branch.
- Monitor deployments closely when pushing to Production.

---