3 ms·
You don't necessarily want to publish all branches to your main project repository, just long-running ones or those that many people hack on. For most branches
by JoshTriplett 15y ago
You don't necessarily want to publish all branches to your main project repository, just long-running ones or those that many people hack on. For most branches, especially experiments, use a branch in a personal repository instead. You can merge from that repository to the main repository if the experiment works out, and otherwise leave it around as an experimental repository and/or archive it. Look at git.kernel.org for an example: linux/kernel/git/torvalds/linux.git only has a "master" branch, but numerous other repositories exist for experiments and development.
That said, I'd also love to see a mechanism for version-control of historical branches. Perhaps something like a reflog with expiration turned off.