-
|
How do you handle changes that need to go into multiple branches? Does it make sense to cherry-pick? Can git-branchless be used to later update both commits together? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Cherry-picking is probably the best way to handle it. git-branchless uses the same "patch ID" mechanism as Git to detect patches which are duplicated across multiple branches, so if you were to There isn't currently a way to update two commits in different places with the same contents. See #553 for more discussion. |
Beta Was this translation helpful? Give feedback.
Cherry-picking is probably the best way to handle it. git-branchless uses the same "patch ID" mechanism as Git to detect patches which are duplicated across multiple branches, so if you were to
git moveorgit syncone branch onto another, then git-branchless to decline to reapply the same patch.There isn't currently a way to update two commits in different places with the same contents. See #553 for more discussion.