You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When setting your mergeStrategy to toReleaseBranch, Ship.js creates a merge commit in the develop branch (merges master back). This creates a messy history, and doesn't make both branches exactly equal (same head, same tag) at a given moment, which is what one may want.
Describe the solution you'd like
It would be nice to be able to specify whether we want to merge or rebase:
module.exports={mergeStrategy: {toReleaseBranch: {develop: 'master',},mode: 'rebase',// or 'merge'},};
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When setting your
mergeStrategy
totoReleaseBranch
, Ship.js creates a merge commit in thedevelop
branch (mergesmaster
back). This creates a messy history, and doesn't make both branches exactly equal (same head, same tag) at a given moment, which is what one may want.Describe the solution you'd like
It would be nice to be able to specify whether we want to
merge
orrebase
:The text was updated successfully, but these errors were encountered: