1
When I fork a repository all of the branches from the upstream repository come with it. Sometimes there are an overwhelming number of upstream branches when I only really care about the branches I'm working on. It seems redundant to have the same branches in two repositories when I can set up both remotes in my local repository.
For example:
Repository A has branches A1,...,A1000. When I fork this repository in GitHub, I get a new repository B with the same branches (A1,...,A1000). I would like repository B to only have the branches I am working on (e.g., B1 and B2).
Is it possible (and even advised) to remove upstream branches from my fork to make things simpler/cleaner for me and my team (i.e., the only branches in our fork are branches we are working on)? Do I at least still need the default branch from upstream repository?
1You can do whatever you want with the forked one. – Biswapriyo – 2019-12-16T19:50:09.697
@Biswapriyo, can you think of any negative impacts on functionality or workflow? Do I need to keep the default branch (or define a new one)? – Neal Kruis – 2019-12-16T19:58:54.997
It depends on what you want to do with the forked repository. If you want to send pull request then there may be some issue but GitHub allows to PR to any branch. – Biswapriyo – 2019-12-16T20:43:59.040