Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certainties about git #1

Open
MichaelDimmitt opened this issue Jul 26, 2018 · 0 comments
Open

Certainties about git #1

MichaelDimmitt opened this issue Jul 26, 2018 · 0 comments

Comments

@MichaelDimmitt
Copy link
Member

MichaelDimmitt commented Jul 26, 2018

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.

@MichaelDimmitt MichaelDimmitt added bug Something isn't working information and removed bug Something isn't working labels Jul 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant