26
submitted 1 year ago* (last edited 1 year ago) by provisional to c/git@programming.dev

I basically only use git merge like Theo from T3 stack. git rebase rewrites your commit history, so I feel there's too much risk to rewriting something you didn't intend to. With merge, every commit is a real state the code was in.

you are viewing a single comment's thread
view the rest of the comments
[-] Mikina@programming.dev 4 points 1 year ago

What does git pull rebase do? If I understand it correctly, it pulls in the remote changes but rebases your changes to be on top of them, instead of merging the remote and local branch? What is the intended usage of it, it sounds like a lot better way how to pull, why not to use it as default pull?

[-] snowe@programming.dev 4 points 1 year ago

you pretty much should use it as the default pull. There are very few cases when you shouldn't use it. Something like fetching from an upstream remote maybe.

[-] GitProphet 1 points 1 year ago

Because rebasing changes the history, which would mess with other people's copies of the same branch, wherefore it shouldn't be default.

this post was submitted on 25 Jun 2023
26 points (100.0% liked)

Git

2911 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS