git commit .Источник: Git в реальной жизни
cli for small things, IntelliJ for smart merging, stashing and unstashing. That's all I need, for many years.
I have a pretty negative attitude to cherry-picking. Rebase - no big deal. No clue what "fixup commit" is.
The rest is in cli and in scripts.
>cat ~/nb git fetch git branch "$1" origin/master
>cat push git commit -a -m "$1" && git push
That's all I do (this is my home machine; a bit more complicated on my work machine).
> git commit --fixup=COMMITHASH > git rebase --autosquash ...
Спасибо за линки! Интересные штучки. Поизучаю.
Other options:
no subject
cli for small things, IntelliJ for smart merging, stashing and unstashing. That's all I need, for many years.
no subject
cherry-picking? rebase? fixup commits? commit-to-branch? routine operations like merge-PR-delete-remote-branch-delete-local-branch-pull-master? regular things.
https://github.com/nvie/git-toolbelt
https://github.com/wfxr/forgit
no subject
I have a pretty negative attitude to cherry-picking. Rebase - no big deal. No clue what "fixup commit" is.
The rest is in cli and in scripts.
That's all I do (this is my home machine; a bit more complicated on my work machine).
no subject
By fixup commit I meant
no subject
But it's extremely helpful when you need to copy fixes from the developer branch to the release branch. And shit happens, you know.
no subject
Спасибо за линки! Интересные штучки. Поизучаю.