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

Squashing commits on PR results in one change detected #118

Open
Andreas1331 opened this issue Mar 24, 2024 · 1 comment
Open

Squashing commits on PR results in one change detected #118

Andreas1331 opened this issue Mar 24, 2024 · 1 comment

Comments

@Andreas1331
Copy link

I am creating a new branch, and every commit on this branch is following the naming convention as described on https://www.conventionalcommits.org/en/v1.0.0/

fix: Fixing something
feat: A new feature

and so on.

If I create PR and squash the commits the title will resemble the branch name, and the body of the commit will be the combination of all commits as expected. However, Versionize does not seem to recognize the body as a 'footer', and create a changelog based on the commit body.
If I instead choose to do a merge, and throw every commit back into the main branch, it works as expected. I realise that the title of a commit must match the required pattern of a type followed by colon, space and a message. I was hoping to use Versionize by automatically generating my changelog and bumping the version based on a squash commit which contains multiple changes.

I have the GitHub Action up and running for this, but I'm struggling a bit to make it work with PR's that use the squashing functionality.

Maybe this is not possible, and I've misunderstood something and the idea is instead to create one branch for one fix or one feature. Then squash into main, and run the Versionize manually once there's x-amount of commits. As I do not want to create a single branch, and update the changelog with a single element everytime I make a PR.

@cabauman
Copy link
Contributor

Mind sharing the github action you mentioned?

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

2 participants