Skip to content

fix vercel deploys #225

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jjavieralv merged 1 commit into from
Jun 10, 2026
Merged

fix vercel deploys #225

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions scripts/vercel-build.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,15 @@
set -o xtrace -o errexit

# Determinar qué playbook usar según la rama
# NOTA: el clone de Vercel no tiene refs de ramas (solo una rama sintética
# llamada "master" apuntando al commit desplegado), así que los sources
# locales deben usar HEAD en vez del nombre real de la rama.
if [ "$VERCEL_GIT_COMMIT_REF" = "master" ]; then
PLAYBOOK="playbook-master.yml"
sed "s|branches: master|branches: HEAD|g" playbook-master.yml > playbook-vercel.yml
PLAYBOOK="playbook-vercel.yml"
elif [ "$VERCEL_GIT_COMMIT_REF" = "staging" ]; then
PLAYBOOK="playbook-staging.yml"
sed "s|branches: staging|branches: HEAD|g" playbook-staging.yml > playbook-vercel.yml
PLAYBOOK="playbook-vercel.yml"
else
# Para cualquier otra rama (previews), generar playbook con URL dinámica
# y usando HEAD para los sources locales
Expand Down
Loading