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
Some people like to keep release notes in the repo.
To do so generally means a release note update commit for every commit on trunk (aka. 50% git history noise) since dripip is designed for making a canary release for every trunk commit.
Dripip should make that possible though for those that want this tradeoff. They have the following options to be specific:
accept 50% git history noise
don't make canary releases
don't update the release notes on canary releases
I can't think of any other ways to trade things off.
The text was updated successfully, but these errors were encountered:
Some people like to keep release notes in the repo.
To do so generally means a release note update commit for every commit on trunk (aka. 50% git history noise) since dripip is designed for making a canary release for every trunk commit.
Dripip should make that possible though for those that want this tradeoff. They have the following options to be specific:
I can't think of any other ways to trade things off.
The text was updated successfully, but these errors were encountered: