chore: Automate Chromatic and TSDiffer runs (#10005)
* adding initial automated api diff process
* tentative github action job
* chromatic workflow and update token naming
* maybe use github model since I dont have a anthropic token and update readme
* lower permisisons
* fix missing repo name in prompt
* update readme
* error messaging and simplification
* try a dry run
* trigger workflow test
* tested differ, change channel for chromatic testing
* whoops messed up the formatting
* finished testing, confirmed behavior
* actually need to test no diff detected case
* fix fail due to diff having been already commited and dont push stder into diff file
* empty commit, this should return nothing
* handle case where new release happens runs and check last diff repo commit rather than just last week
the latter is to handle the case where we run this flow multiple times a day or in the same week and there arent any new changes. Previously it would still use the current weeks diff results rather than reporting that there are no changes
* add clarity for various diff cases
running diff right after new release when there are new changes, running diff between releases, where there are no changes between last run, and when there are no changes from the released code
* still got a diff message... try something else
* invalid yarn option ugh
* empty commit after new baseline, this should return nothing
* done with testing
* update readme and prompt
* Apply suggestions from code review
Co-authored-by: Daniel Lu <danilu@adobe.com>
* make it clear to AI model that it comparing a diff of diffs
hopefully this make it so it can reason that a new api change to a component/prop that didnt have changes last week isnt actually a brand new component
