Replies: 1 comment 3 replies
-
We split the list of packages into changes and not changed packages - so we do recognize which packages you have worked on.
Conceptually there is no 1-to-1 relationship between your changes and changesets. You are free to add more than one changeset per package and you are free to create different changesets for different packages for the very same "change". Those are not coupled. For each package that has been affected by your changes you probably should write a changelog entry from its own perspective.
Perhaps you are looking for a |
Beta Was this translation helpful? Give feedback.
-
please help me understand this tool in regards with monorepo (turborepo)
why doesn't changesets see which package in the monorepo i have worked on in the commit ? why does it ask the developer to choose ?
how can i allow the developers to commit without writing the changeset and only describe the changes when they are ready ? when working most developer commit small changes not a the big one. how can that work ?
Beta Was this translation helpful? Give feedback.
All reactions