You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certainty, no1:
Clone a project and push it to another remote with no history it will only take your local.
Certainty, no2:
git fetch --all,
any remote branch does not have local overhead.
Your branch only contains the overhead of what it has stored locally.
When you push what you have locally to another remote it will only grab your local changes.
try it yourself,
git remote add icecream
git push icecream --all
Certainty, no3:
this means that whatever you individually push will only go to that specific remote
and what you individually clone or checkout will only go to your local.
if you rebase, old sha's are stored on your computer but they are not persisted to where if someone does a fresh clone on a project with changes you push to github. Those sha's that were not in the branches pushed will not show up on their computer.
having sha's are useful for recovering a project to a specific point in case something goes wrong.
Certainty, no4:
If you squash your branches to a single branch and then squash your commits to remove the bloat your can reboot your project removing the bloat without losing the history.
Certainty, no5:
if you do have remote branches, git will stay bloated on the off-chance that you choose do checkout that branch so that it does not take forever to do that checkout operation.
The text was updated successfully, but these errors were encountered:
Certainty, no1:
Clone a project and push it to another remote with no history it will only take your local.
Certainty, no2:
git fetch --all,
any remote branch does not have local overhead.
Your branch only contains the overhead of what it has stored locally.
When you push what you have locally to another remote it will only grab your local changes.
try it yourself,
git remote add icecream
git push icecream --all
Certainty, no3:
this means that whatever you individually push will only go to that specific remote
and what you individually clone or checkout will only go to your local.
if you rebase, old sha's are stored on your computer but they are not persisted to where if someone does a fresh clone on a project with changes you push to github. Those sha's that were not in the branches pushed will not show up on their computer.
having sha's are useful for recovering a project to a specific point in case something goes wrong.
Certainty, no4:
If you squash your branches to a single branch and then squash your commits to remove the bloat your can reboot your project removing the bloat without losing the history.
Certainty, no5:
if you do have remote branches, git will stay bloated on the off-chance that you choose do checkout that branch so that it does not take forever to do that checkout operation.
The text was updated successfully, but these errors were encountered: