From b1a4ecbb7afec171381e906d088e086309c5163f Mon Sep 17 00:00:00 2001 From: Sebastian Ricaldoni Date: Tue, 17 Mar 2026 13:04:44 -0300 Subject: [PATCH] Trigger TestFlight release for issue #207 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Phony README fix (typo: Spacification → Specification, property → properly) to trigger a new TestFlight build via the CD pipeline. Closes #207 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7082b76..036d3f4 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ The application includes continuous integration (CI) and continuous delivery (CD - Automatically build and test the application on every pull request before deploying it. - An automated setup to deploy the application to TestFlight every time there is a new commit on the repository's main branch. - Ensure a coherent code style by checking the conformance to the SwiftLint rules defined in `.swiftlint.yml` on every pull request and commit. -- Ensure conformance to the [REUSE Spacification]() to property license the application and all related code. +- Ensure conformance to the [REUSE Specification]() to properly license the application and all related code. Please refer to the [StanfordBDHG Template Application](https://github.com/StanfordBDHG/Balance) and the [ContinousDelivery Example by Paul Schmiedmayer](https://github.com/PSchmiedmayer/ContinousDelivery) for more background about the CI and CD setup for the CardinalKit Template Application.