-
Notifications
You must be signed in to change notification settings - Fork 243
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 #757
Labels
Comments
Are you having success with the pull prototype? |
this may help: https://stackoverflow.com/questions/39651287/doing-a-git-pull-with-libgit2 it talks about checkout having the wrong default strategy |
This new command (lg2) should enable pulling using a terminal command: #887 |
bummoblizard
added a commit
to bummoblizard/codeapp
that referenced
this issue
Aug 8, 2023
bummoblizard
added a commit
that referenced
this issue
Aug 9, 2023
git: pull with fast-forward merge #757
Pulling with / without conflicts is now supported. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Users are often confused by fetch and pull. The expect the local directory to change when they press fetch. We should support this behaviour by introducing pull feature.
Git pull = fetch + merge
We can ignore the case with conflicts for now. So it will just be fetch + checkout to remote branch.
The text was updated successfully, but these errors were encountered: