3 ms·
"you don't type git pull every time, do you?" No, I fetch and then merge. "Put those to your .bashrc or .zshrc" git aliases should be added to gitconfig to a
by dfc 14y ago
"you don't type git pull every time, do you?"
No, I fetch and then merge.
"Put those to your .bashrc or .zshrc"
git aliases should be added to gitconfig to avoid muddying the global namespace for commands.
- ambrice 14y agoIt's not a git alias. It would be better to do this as a post-merge hook though.
- dfc 14y agoI know it is not a gitalias, it is a shell wide alias for a command that involves git. That is why I said the better solution would be to use gitalias than your shell's alias functionality. With gitalias you can provide the same functionality without creating the possibility for command conflicts.
- medwezys 14y agoI don't like merge commits when you can avoid them.
- waffle_ss 14y agoIndeed... git pull --rebase is your friend (or better yet, set rebase as default strategy for pulls)
- yhager 14y agoI don't know how to run a shell alias using a git alias, so I ended up creating a file ~/bin/fact, and defining the git alias as: [alias] ff = "!fact && git fetch"