Test reporting isn’t the most critical aspect, just an example of something GHA leaves for third party tools to implement.
With CurcleCI, looking through docs, the biggest concern is integration with GitHub. Reading limitations of both OAuth and GitHub App integrations it looks like there’s a race to catch-up with changes a limitations on GitHub side. Not sure if it’s GH not exposing some functionality to third parties to differentiate Actions (e.g. GHA having many more trigger events available) or is that CircleCI needs more time to implement missing features through GitHub App integrations.
Thanks for clarifying, appreciate it! It's true we don't support all the events that Github exposes, but we believe we support the most common and useful ones. Also, this is not set in stone and expanding all the time, f.e. https://circleci.com/changelog/trigger-pipelines-on-github-p...
With CurcleCI, looking through docs, the biggest concern is integration with GitHub. Reading limitations of both OAuth and GitHub App integrations it looks like there’s a race to catch-up with changes a limitations on GitHub side. Not sure if it’s GH not exposing some functionality to third parties to differentiate Actions (e.g. GHA having many more trigger events available) or is that CircleCI needs more time to implement missing features through GitHub App integrations.