Граф коммитов

1 Коммитов

Автор SHA1 Сообщение Дата
Timothee Guerin 3040a83d6d
Chronus changelogs (#2851)
Issues with changesets versioning that prevent us from using it:
1. This one is a deal breaker bug that bumps to major versions(when we
try to bump todays changelog everything gets bumped to 2.0.0) (This is a
bug we found happened sometimes in cadl-ranch but this just happens
immediately in our repo due to everything being linked)
2. the verify doesn't check all packages have changelog just that there
is at least one
3. the `changesets add` doesnt' compare against remote main but local
main so you endup with confusing saying other packages changes if you
pulled some change from main in your branch but not on your local main


## Example of auto created comment

When changes are needed

![image](https://github.com/microsoft/typespec/assets/1031227/f20a0708-1d28-444b-be07-6ededcb5e3c1)

When everything is documented 

![image](https://github.com/microsoft/typespec/assets/1031227/9c0d0d05-d882-4f6e-87a5-3a58301fea49)

## Error is also more readable


![image](https://github.com/microsoft/typespec/assets/1031227/a7d0de43-4fed-4f01-94ba-3f95ae210c5d)

## `chronus add` experience

![image](https://github.com/microsoft/typespec/assets/1031227/ba31c84e-f2bf-4bfb-b754-743f2a78199a)

![image](https://github.com/microsoft/typespec/assets/1031227/922a5afc-e076-4d5c-91fc-df95bf423f04)

![image](https://github.com/microsoft/typespec/assets/1031227/98f2cedb-1783-42ed-930a-2d626de5c642)
2024-02-01 14:07:24 -08:00