git - "Safe" rebasing after branch has been pushed already -
i have following situation, happens quite me/us:
i branched some_feature
master
. lets call me main developer of feature. @ point pushed branch remote origin
, remote colleague did small changes, pushed them , pulled them. in mean time, master
has changed. because want have clean history, prefer rebase instead of merging, problem, because branch has been pushed.
the best idea had, create new local branch based on some_feature
, rebase one. way, some_feature
should not modified, commits should replayed onto latest master
, in case ever push branch, should safe.
can confirm workflow not harm coworkers or propose better workflow situation?
Comments
Post a Comment