Conversation
Limiting to just iPhone for now
Dynamically determine the newest iPhone model and run tests on that
Using ci-core.yml to centralize the logic to build and generate code coverage data
Code Coverage
|
…lts if they exist
|
Thanks a lot for putting this together and for iterating on the CI setup. I’m closing this PR because the CI work has been superseded by the newer maintenance/CI updates on The current CI now covers the main validation paths we need for PRs and pushes:
This PR also contains a large experimental reusable-action/coverage setup and now conflicts with the updated workflow structure. Rather than merging it as-is, we should keep the current CI as the baseline. The coverage-reporting and simulator-selection ideas are still useful. If we want to revisit them, they would be very welcome as smaller PRs based on the latest Thanks again for the contribution and for helping move the project’s CI forward. |
|
@iziz - No worries...I was just iterating on it to try to get it working (and also experiment on using AI to help code up all the github action logic). I saw that you went ahead and did your own thing, so yeah...I will hopefully get a chance to revise this work, and start building off of what you did to add additional features in the future). |
Limiting to just iPhone for now