You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Me and my team would like to port Changesets tool to .NET world.
We need to manage automatic versioning, changelog generation and Nuget package releases in mono repo. We really like the principles which Changesets brings and we would like to bring it to .NET world!
The idea is to create Changesets as dotnet tool. Instead of package.json the tool would work with .csproj. Instead of npm repository the tool would publish nugets to nuget repository. The flow with generating changesets and CHANGELOG.md from changesets would stay the same.
The CLI would stay the same. The only difference would be, instead of calling npm
npm changeset add
npm changeset version
we would call dotnet
dotnet changeset add
dotnet changeset version
Ofc other commands would be also ported, they are just not mentioned here.
We would like to reuse your GitHub release action.
Would you accept PR which would refactor current Action to work also with dotnet tool? We do not have any specific solution right now, we would like to know your thoughts about this.
If we will feel ready we would publish changeset dotnet tool here on GitHub as opensource project.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello Changesets Team!
Me and my team would like to port Changesets tool to .NET world.
We need to manage automatic versioning, changelog generation and Nuget package releases in mono repo. We really like the principles which Changesets brings and we would like to bring it to .NET world!
The idea is to create Changesets as dotnet tool. Instead of package.json the tool would work with .csproj. Instead of npm repository the tool would publish nugets to nuget repository. The flow with generating changesets and CHANGELOG.md from changesets would stay the same.
The CLI would stay the same. The only difference would be, instead of calling npm
we would call dotnet
Ofc other commands would be also ported, they are just not mentioned here.
We would like to reuse your GitHub release action.
Would you accept PR which would refactor current Action to work also with dotnet tool? We do not have any specific solution right now, we would like to know your thoughts about this.
If we will feel ready we would publish changeset dotnet tool here on GitHub as opensource project.
Thanks!
Marek
Beta Was this translation helpful? Give feedback.
All reactions