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

Support for filtering merge commits #1046

Open
anthonyoteri opened this issue Oct 23, 2024 · 0 comments
Open

Support for filtering merge commits #1046

anthonyoteri opened this issue Oct 23, 2024 · 0 comments
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@anthonyoteri
Copy link

Is your feature request related to a problem? Please describe.
I have the Pull Requests: Merge Commits title set to use the PR title instead of the default message. On branches with a single commit, the default title for the PR is the same as the single commit. This leads to 2 commits with the same message in the main branch, which then gets picked up by this action and I get duplicate entries in the changelog. One entry for the regular commit, and one for the merge commit.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
See above.

Describe the solution you'd like
It would be good to have some kind of configuration option in the config file to filter merge commits so that these duplicates can be avoided.

Describe alternatives you've considered
Manually editing the release notes after release, which is a workaround at best.

@anthonyoteri anthonyoteri added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Oct 23, 2024
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: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants