原文
| ||||||||||
| ||||||||||
 | ||||||||||
（评论）
(comments)
原始链接: https://news.ycombinator.com/item?id=43860431
一个 Hacker News 的帖子讨论了“Git Changesets”这个工具（github.com/changesets），它用于管理版本控制和变更日志，尤其是在单体仓库中。发帖者质疑该项目声称 Git 不鼓励详细的变更描述的说法，并认为可能是 Github 的 UI 才是罪魁祸首。另一位评论者指出，该项目与 Git 或 Github 并没有官方关联，标题具有误导性。他们建议将标题修改为使用项目的标语：“Changesets——专注于单体仓库的版本控制和变更日志”（或略微修改后的版本）。他们还请求版主考虑更改标题。
> 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...
reply