Ian Davis

Are you talking about making it less chatty, or changing the notifications?

One thing is to try to determine which tests should be run. You can try to do convention such as changes to Foo will run Foo\* tests, or use the...

If you want less, what about only notifying on state change? ``` S=>BuildFailed S=>BuildPassed BuildFailed=>BuildPassed BuildPassed=>BuildFailed BuildPassed=>TestsFailed BuildPassed=>TestsPassed TestsFailed=>TestsPassed TestsFailed=>BuildFailed TestsPassed=>BuildFailed TestsPassed=>TestsFailed ```

OT: The other thing I would suggest is changed the good to go icon to green instead of orange/yellow check mark.

Where do you think it would be the most helpful? Failing on the command line? Wiki?

@messense I have created a PR for [Adding license_expression and license_files serialization](https://github.com/PyO3/pyproject-toml-rs/pull/2) to support this work in the `PyO3/pyproject-toml-rs` repo.

@messense Submitted PR #862 which has just the default license packaging from PEP 639. The other items in this issue require the serialization updates.

Do we need all of these installed? Are these just needed for building or do we shell out to them? ```shell # We don't use openssl (3.0) for now. We...

This will be handled when updating to support the adaptive profile specification.

Fixed by #36