Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enable automatic pruning of stale remote-tracking refs so the local clone stops accumulating zombie
origin/*refs after GitHub deletes branches on merge.Adds to the repository
.gitconfig:fetch.prune = true— every fetch/pull now removes remote-tracking refs whose branch has been deleted on the remote (e.g. GitHub's "automatically delete head branches").push.autoSetupRemote = true— the first push of a new branch sets its upstream automatically.Context
When a PR is merged with auto-delete enabled, GitHub deletes the remote branch but the local remote-tracking ref (
refs/remotes/origin/<branch>) lingers until an explicitgit fetch --prune. Withfetch.prunethis is now automatic. Note this prunes only the remote-tracking ref; the local branch itself is still kept (Git never deletes local branches implicitly) and shows[gone]as a signal to clean it up.Testing
git fetch --prune originremoved the two stale refs (origin/changeset-release/main,origin/fix/marketplace-tag-on-main).git config --show-origin --get fetch.pruneresolves to the repository.gitconfig(included via globalinclude.path), confirming the wiring.Notes
.gitconfigis consumed via a globalinclude.pathentry; the file itself is tracked so the setting travels with the repo.