GitHub Flow y Ramas de Release

GitHub Flow (adaptación móvil)
  1. Rama desde main     → feat/SHIP-220-dark-mode
  2. Abre PR              → CI + evidencia de dispositivo requerida
  3. Fusiona a main        → squash preferido
  4. Despliega               → OTA a canal preview O tag para compilación de store

# Hotfix para versión de store en vivo 2.4.x (paralelo a 2.5 RC en release/2.5.0)
git fetch --tags
git checkout -b hotfix/2.4.2 v2.4.1
git cherry-pick <fix-sha>
git tag -a v2.4.2 -m "Hotfix: crash on cold start [SHIP-991]"
git push origin hotfix/2.4.2 v2.4.2

# Hotfix solo de JS en el mismo runtimeVersion - OTA desde rama hotfix
git checkout hotfix/2.4.2
eas update --branch production --channel production --environment production \
  --message "hotfix: cold start crash [SHIP-991]"

Ejemplo de carriles paralelos
  main              ← integración
  release/2.5.0     ← RC en revisión de TestFlight
  hotfix/2.4.2      ← usuarios de store 2.4.x en production
  (OTA production channel ← hotfix/2.4.2 commits only)

<!-- docs/branch-channel-map.md -->
| Rama Git         | Versión de Store | Rama EAS Update | Canal EAS    |
|------------------|------------------|-----------------|--------------|
| main             | (siguiente)      | preview         | preview      |
| release/2.5.0    | 2.5.0 RC         | staging         | staging      |
| hotfix/2.4.2     | 2.4.2 en vivo    | production      | production   |

eas channel:view production
# Confirma que el canal apunta a la rama production - no a main

git checkout main && git pull --ff-only
git checkout -b fix/SHIP-991-cold-start
# ... fix ...
git commit -m "fix(app): guard null session on cold start [SHIP-991]"
git push -u origin fix/SHIP-991-cold-start
# PR → squash merge a main

git fetch --tags
git checkout -b hotfix/2.4.2 v2.4.1
git cherry-pick <squashed-sha-from-main>
npm run typecheck && npm run test -- --ci
git push -u origin hotfix/2.4.2

# Incrementa versión de app solo en rama hotfix
# app.json → version 2.4.2, ios.buildNumber++, android.versionCode++
 
git commit -am "chore(release): bump to 2.4.2 [SHIP-991]"
git tag -a v2.4.2 -m "Hotfix 2.4.2 - build_id xyz789"
git push origin hotfix/2.4.2 v2.4.2

git checkout hotfix/2.4.2
eas update --branch production --channel production --environment production \
  --message "hotfix: cold start [SHIP-991]"

# Verifica que el head del canal production coincida con el tip de hotfix
git rev-parse hotfix/2.4.2
eas update:list --branch production --limit 1

# main ya tiene el fix del paso 2
git checkout release/2.5.0 && git pull --ff-only
git cherry-pick <same-sha>
git push origin release/2.5.0

# Listar ramas aún recibiendo OTA
git branch -r | grep -E 'hotfix|release'
eas channel:list

# Documentar en CONTRIBUTING.md - imponer en GitHub Settings
main:
  required_checks: [quality, pr-template]
  required_reviews: 1
  allow_force_push: false
 
release/*:
  required_checks: [quality, maestro-smoke]
  required_reviews: 2
  restrict_push: [release-managers]
 
hotfix/*:
  required_checks: [quality]
  required_reviews: 2  # expedido pero no en solitario