# EnCoach Backend — v2

## Branching Workflow

This repo is connected to the staging server via a Git post-receive hook.
**All deployment is automatic — but only after code review approval.**

### How to contribute

1. Never push directly to `main` — branch protection will block it.
2. Create a feature or fix branch:
   ```bash
   git checkout -b feature/your-feature-name
   ```
3. Develop, commit, and push your branch:
   ```bash
   git push origin feature/your-feature-name
   ```
4. Open a **Pull Request** on Gitea targeting `main`.
5. Request review from **devops (Talal)**.
6. Once approved and merged, the staging server rebuilds and redeploys automatically.

### Environment

The `.env` file is **not committed**. It lives only on the staging server at `/opt/encoach/backend-v2/.env`.
Contact the team lead if you need a local copy of the environment variables.

### Required files (push with your code)

- `Dockerfile` — used by the staging server to build the container image
- `docker-compose.yml` — defines the backend service (port mapping, env vars, etc.)
# Pipeline test Mon Mar 30 19:42:50 +04 2026
