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.

Informations de source

Dépôt
thisrohangupta/v0-harness-documentation-website
Dernière activité de la source
3 mars 2026 à 06:12
Langue détectée de SKILL.md
anglais
Étoiles
1
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
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
Voir sur GitHub