Skip to main content

sync-branches

Sync commits to both main and v0/rohangupta-dec27c78 branches. Use after committing changes, when pushing code, or when asked to sync branches. Ensures both branches stay in lockstep.

Datos de origen

Repositorio
thisrohangupta/v0-harness-documentation-website
Última actividad en el origen
3 de marzo de 2026 a las 06:12
Idioma detectado de SKILL.md
inglés
Estrellas
1
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
sync-branches
description
Sync commits to both main and v0/rohangupta-dec27c78 branches. Use after committing changes, when pushing code, or when asked to sync branches. Ensures both branches stay in lockstep.
disable-model-invocation
true
allowed-tools
Bash(git *)
# Sync Both Branches After committing changes, sync them to both `main` and `v0/rohangupta-dec27c78` branches. Both branches MUST always stay in sync. ## Steps 1. **Confirm current state** - Run `git status` to ensure the working tree is clean - Run `git log --oneline -3` to identify the commit(s) to sync - Note the current branch 2. **If on `main`:** ```bash git checkout v0/rohangupta-dec27c78 git cherry-pick <commit-hash> git checkout main ``` 3. **If on `v0/rohangupta-dec27c78`:** ```bash git checkout main git cherry-pick <commit-hash> git checkout v0/rohangupta-dec27c78 ``` 4. **Push both branches:** ```bash git push origin main git push origin v0/rohangupta-dec27c78 ``` 5. **Return to the original branch** the user was on. ## Rules - NEVER force push - NEVER push to only one branch — both must be updated - If cherry-pick has conflicts, stop and ask the user for guidance - If there are uncommitted changes, stop and ask the user to commit first - Always verify both branches have the same HEAD commit after sync
Ver en GitHub