From the "detailed explanation" document (my emphasis):
When organising the release of packages, you may end up wanting to group several changes together written by different people and/or over a relatively large period of time. The best time to capture this information is when submitting a PR (when it is fresh in your mind), not when you eventually go to batch and release these changes.
Git is a bad place to store this information, as it discourages writing detailed change descriptions - you want to allow people to provide as much documentation for the change as they want.
How does Git discourage writing detailed change descriptions? Is this a Github thing, i.e. the web UI workflows discourage it? I use Git a lot but barely use Github.
The title made me think this was an official feature of git or maybe GitHub, but it's entirely unrelated - in fact, the readme doesn't even mention git.
I'd suggest changing the title to actually use the project tagline: "Changesets - versioning and changelogs with a focus on monorepos" (possibly s/with a focus on/for/)
Comments
From the "detailed explanation" document (my emphasis):
How does Git discourage writing detailed change descriptions? Is this a Github thing, i.e. the web UI workflows discourage it? I use Git a lot but barely use Github.
https://github.com/changesets/changesets/blob/main/docs/deta...
The title made me think this was an official feature of git or maybe GitHub, but it's entirely unrelated - in fact, the readme doesn't even mention git.
I'd suggest changing the title to actually use the project tagline: "Changesets - versioning and changelogs with a focus on monorepos" (possibly s/with a focus on/for/)
(@dang @tomhow)
So much words in the docs. So little explanation of why