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

The Github Releases Only Ever Include The Most Recent PR/Squashed Merge Commit #27

Open
Grunet opened this issue May 4, 2022 · 0 comments

Comments

@Grunet
Copy link
Owner

Grunet commented May 4, 2022

I thought release-it was supposed to include all commits since the previous tagged release, but maybe I misunderstood (or the defaults)

I haven't looked into this yet, but I suppose a workaround is to manually edit the release notes afterwards to give more info on what's changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant