Does GitHub garbage collect dangling commits referenced in pull requests?
The following situation arises from time to time…
git checkout -b experiment, commit some experimental changes, and open a pull request. After some discussion, the pull request is rejected.
Switching branches without touching the working tree? Git pull reverted commits in master? Why are deleted branches not removed on the remote after pushing? git push to different branches on multiple remotes Centralized GIT workflow/deployment - Repository Initialization and Feature Branches What are the differences between GIT and SVN when it comes to merge conflicts solving
If I were now to delete the remote branch, would this render the diff inaccessible at some point, or does GitHub ensure that commits which appear in pull requests are not garbage collected even if they don’t appear on any branch?
I would like to delete dead branches, but only if doing so will not diminish the historical value of rejected pull requests.
One Solution collect form web for “Does GitHub garbage collect dangling commits referenced in pull requests?”
No, they will not be gc’s because they’re not wholly unreferenced even if you delete your branch.
Github creates a branch (actually, two) for every pull request. They’re in a non-default namespace so you dont usually get them when you pull (or fetch) from the repo.
To see how this looks in practice, do a
git ls-remote <REMOTE>, where
<REMOTE> is either the name of a remote (if it’s one your repo knows) or the URL (it doesn’t need to be
git remote added for this to work). This remote should have some pull requests, or you won’t be able to see what I mean.
This will list all refs on the remote (all branches and tags), and you will see some refs like
refs/pull/<number>/merge. Those refer to the latest commit in the PR and the commit at which it was merged in, respectively.