Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in-repo changelogs #100

Open
jasonkuhrt opened this issue Nov 23, 2020 · 0 comments
Open

in-repo changelogs #100

jasonkuhrt opened this issue Nov 23, 2020 · 0 comments
Labels
scope/release-notes type/feat Add a new capability or enhance an existing one

Comments

@jasonkuhrt
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/release-notes type/feat Add a new capability or enhance an existing one
Projects
None yet
Development

No branches or pull requests

1 participant