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

melos version to support cherry-picks #666

Open
1 task done
Gustl22 opened this issue Mar 19, 2024 · 0 comments
Open
1 task done

melos version to support cherry-picks #666

Gustl22 opened this issue Mar 19, 2024 · 0 comments

Comments

@Gustl22
Copy link

Gustl22 commented Mar 19, 2024

Is there an existing feature request for this?

  • I have searched the existing issues.

Command

melos version --fix-changelog

Description

If having bug fixes or smaller features which are cherry-picked into a separate "release" branch, the changelog is created accordingly. Then the changelog is cherry-picked into the main branch.
Is there some mechanism to avoid having duplicate entries (when doing a further e.g. major release on main) then, or even let melos fix the existing entries by changing the hash of cherry-picked commits?

Reasoning

Now I have to adapt the changelog manually, to remove duplicate entries / change the hashes.

Additional context and comments

No response

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

No branches or pull requests

1 participant