Open YuhanLiin opened 1 year ago
no real reason but that we haven't gotten to it :)
Some previous discussions on this
https://github.com/rust-embedded/svd2rust/pull/542#issuecomment-934170012
I've previously also mentioned the possibility to use something like bors try --regress
to catch changes in prs and print them as comments, with the new github cli I think we can do this easily and improve the experience.
cc @Emilgardis should CI be replaced with svd2rust-regress test
?
I think it could and probably should
The CI script seems to do the exact same thing as
svd2rust-regress
, so I'm wondering why they're separated.