Комментарии:
git push --force
ОтветитьSince rebase will rewrite the commit history, a good rule of thumb is to only rebase on branches that are fully in your control - ie. No one else is using that branch. Use merge if others are also working within the same branch.
If you do use rebase on a branch that other people are working with, make sure to communicate that to them so they know they will need to pull down and fix any merge conflicts. I like to stash my changes, pull the changes down and then unstash my previous changes so that I can minimize any conflicts.
Merge, keep it simple stupid.
ОтветитьTeam cherry-pick
ОтветитьRebase is more flexible but it must be used with extra care.
ОтветитьMerge
ОтветитьHey. Make a git tutorial. If you make it. It will be best tutorial 😊
Ответитьcherry-pick commits😅
ОтветитьWork with a lot of people in a short period of time and are more likely to conflict -> Merge
Relatively few conflicts, and the commit history must be managed well. -> Rebase
Rebase is always the best way to go.
ОтветитьHey there, I recommend to have both branches in the remote before rebasing them, because you cannot reset the rebase when there is a problem with your branches and rebase operation
ОтветитьRebase is what my team uses and is ok. You just need to know when to merge
Ответитьrebase is OP when used correctly
ОтветитьI tend to rebase
ОтветитьI vote for rebase :D
ОтветитьTeam rebase
ОтветитьRebase is the best!
ОтветитьIf the goal is to have a really clean commit history, one should consider using squash and learning interactive rebases
ОтветитьNeither. I dont use version control.
ОтветитьRebase
ОтветитьI have seen rebase option many times but never used it
ОтветитьMerge is always easier. Rebase most times generate more complex issues
ОтветитьMost teams I have worked on go with merge as its simpler and safer. I do not trust myself and hard pass on deleting commit history. Seen people f up stuff with rebase.
ОтветитьSingle commit per MR/PR. Always rebase.
ОтветитьI simply like merge but my team lead always says to rebase and create problems
Ответитьrebase is always a problem, one day the team lead just cut out a huge changes that I worked on for a week. had to restore all the lost files, while the packages created by me were preserved, it was very strange
Ответитьgit reset --hard 🎉
ОтветитьRebase
ОтветитьGit rebase is a powerful feature 🔥🔥
ОтветитьI would simply merge 😂. rebasing and fixing conflicts in each commit is a suicide 😂😂
Ответить