Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Process for including in an NPM package? #1119

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

Closed
paul-uz opened this issue Mar 24, 2025 · 0 comments
Closed

Process for including in an NPM package? #1119

paul-uz opened this issue Mar 24, 2025 · 0 comments

Comments

@paul-uz
Copy link
Contributor

paul-uz commented Mar 24, 2025

So I'm a bit confused about how this would work.

I have an NPM package, and I make a new feature. I commit the work to my repo, and the publish to NPM.

I want the changelog, created by git cliff, to be included in the SDK.

But it seems like a chicken and egg kinda situation; I have to make the commits first to create the changelog, but by doing so, that means I have to do another commit to add the changelog.

Whats the correct order of doing things so I'm not adding additional, unneeded commits?

Repository owner locked and limited conversation to collaborators Apr 20, 2025
@orhun orhun converted this issue into discussion #1130 Apr 20, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant