Make CI Change-Aware and Add Release Validation - #64
Merged
Conversation
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PSchmiedmayer
force-pushed
the
feature/granular-ci
branch
from
August 20, 2026 04:55
8289105 to
6c10eb0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
♻️ Current situation & Problem
Grove's Tests workflow currently treats every
Package.swift, CI-infrastructure, and script change as affecting the complete package matrix. This causes unrelated unit and UI jobs to run across the monorepo, while the existing FHIR output validator is not integrated into Grove's CI. There is also no single manual workflow for running every enabled check before a release.⚙️ Release Notes
packages.toml, preventing silent test-selection gaps.macos-latestfor GitHub-hosted macOS jobs.xcbeautifyand GitHub Actions annotations while retaining the complete raw log for repository-specific DocC warning checks.📚 Documentation
This does not add or modify public APIs. The selection rules and conservative fallbacks are documented inline in
Scripts/affected-test-matrix.py;Scripts/ci-dryrun.shmirrors the workflow's manifest-aware selection for local inspection.✅ Testing
PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s Scripts/Tests -p 'test_*.py'actionlint .github/workflows/*.ymlshellcheck Scripts/build-documentation.sh Scripts/ci-dryrun.sh Scripts/validate-fhir-conformance.shbash -n Scripts/build-documentation.sh Scripts/ci-dryrun.sh Scripts/validate-fhir-conformance.shGROVE_ENABLE_DEFAULT_PACKAGE_TRAITS=1 swift build --target GroveHealthKitFHIRScripts/build-documentation.shgit diff --checkThe selector has focused regression coverage for manifest target/product/dependency changes, package configuration changes, FHIR triggers, documentation-only changes, shared CI infrastructure, conservative script handling, and newly added unclassified targets.
The first CI run for this PR intentionally selects the complete suite because the Tests workflow itself changed.
Code of Conduct & Contributing Guidelines
By creating and submitting this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: