Git - Remote Repositories
After renaming a remote branch, your local tracking branch still points to the old name. How to fix this?
After renaming a remote branch, your local tracking branch still points to the old name. How to fix this?
medium📝 Troubleshoot Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Remove stale remote references
Runninggit fetch --prunecleans up old remote branch references.Step 2: Update local branch tracking
After pruning, set the local branch to track the renamed remote branch withgit branch -u origin/new-name.Final Answer:
Run git fetch --prune and then set upstream to new remote branch -> Option AQuick Check:
Prune stale refs then update tracking branch [OK]
Quick Trick: Use 'git fetch --prune' to clean old refs before resetting tracking [OK]
Common Mistakes:
- Expecting tracking to update automatically
- Using git reset --hard which resets files
- Deleting local branch unnecessarily
Master "Remote Repositories" in Git
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Git Quizzes