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

Merge Commits leading to Duplicate Changelog Entries #2476

Open
yzietz-ionos opened this issue Feb 12, 2025 · 0 comments
Open

Merge Commits leading to Duplicate Changelog Entries #2476

yzietz-ionos opened this issue Feb 12, 2025 · 0 comments
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@yzietz-ionos
Copy link

yzietz-ionos commented Feb 12, 2025

Hey guys,

I'm having the issue for some time now, that the release-please app is creating duplicate entries for the same change in case my history contains a merge commit of a feature branch. For example:

commit 903930805b446f7f390845adb356c295392260e1
Merge: 8c9b50d f0735d9
Author: xyz
Date:   Mon Feb 3 15:29:31 2025 +0100

    Merge pull request #178 from BLA/feature/some-feature

    feat: change smth

commit f0735d97ed27f93a50d4323af03f8a0b81210c92 (origin/feature/some-feature, feature/some-feature)
Author: xyz
Date:   Mon Feb 3 15:24:27 2025 +0100

    feat: change smth

leading to

## [1.1.0](https://github.com/BLA/BLUB/compare/v1.0.2...v1.1.0) (2025-02-11)


### Features

* change smth ([9039308](https://github.com/BLA/BLUB/commit/903930805b446f7f390845adb356c295392260e1))
* change smth ([f0735d9](https://github.com/BLA/BLUB/commit/f0735d97ed27f93a50d4323af03f8a0b81210c92))

My unproven assumption is, that #2358 is the cause of that behaviour.

Therefor to my questions:

  1. Can you confirm my assumption or may there be another cause?
  2. Is there a mitigation for that problem other than avoiding merge commits?

Thanks in advance!

@yzietz-ionos yzietz-ionos added priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue. labels Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

2 participants