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

git pull vs. git pull --rebase #17

Open
lsmith77 opened this issue Jan 18, 2012 · 3 comments
Open

git pull vs. git pull --rebase #17

lsmith77 opened this issue Jan 18, 2012 · 3 comments

Comments

@lsmith77
Copy link

the cheat sheet lists "git pull" .. i think as described there its dangerous and will make the main beginner task (keeping in sync with remote code changes without necessarily adding any of their own) needlessly error prone.

@rogerdudler
Copy link
Owner

Hey Lukas! Any suggestions for writing it the correct way?

@lsmith77
Copy link
Author

not really sure either ..

maybe:

merge remote changes into local repository => git pull
synchronize local repository with remote changes => git pull --rebase

@ghost
Copy link

ghost commented Jan 18, 2013

Always use rebase when fast-forward isn't possible. Can't tell you enough how much I hate commit messages that only sais "Merge branch 'master' of #repo#".

http://darwinweb.net/articles/the-case-for-git-rebase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants