by kaishiro on 5/1/25, 5:04 PM with 3 comments
by nemetroid on 5/1/25, 7:37 PM
> 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.
https://github.com/changesets/changesets/blob/main/docs/deta...
by LordDragonfang on 5/1/25, 6:07 PM
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)
by thealistra on 5/5/25, 9:53 PM