I think this is the solution you are looking for: https://developer.apple.com/documentation/xcode/including-notes-for-testers-with-a-beta-release-of-your-app Basically you have to create a text file in the following location: MyApp > TestFlight > WhatToTest.en-US.txt *You can create various localized versions if you want the notes to be available in other languages by replacing the locale code in the filename. To automate it, you will want to run a script in the ci_scripts/ci_post_clone.sh file that creates/updates that text file with your desired notes. I don't think you will need to actually commit those changes since Xcode Cloud has already checked out your repository, but not 100% sure. I haven't verified this all works yet, but I am about to start testing it out for our nightly QA builds by generating that file with the last 24hrs worth of commit messages. I'll post my results here once I go through the whole flow though.

@metolius Yup, it worked for us.

For our purposes we use various QA and automation tools for testing. One of which is Snapshot Testing (https://github.com/pointfreeco/swift-snapshot-testing) for detecting and flagging unexpected UI changes. Apparently the screenshots that Snapshot generates differ slightly when run from Intel v. Apple Silicon machines. This causes every test to fail (hundreds in our case). Our entire iOS developer team use Apple Silicon machines while Xcode Cloud does not, so this is problematic when running unit tests locally before pushing changes which get run on CI (Xcode Cloud). We eventually found a workaround but it seems odd (and counter-productive) for Apple to be pushing for adoption of their own Silicon machines but not using them for a significant platform like Xcode Cloud. Ideally our CI environment would always mirror our local environment. Hopefully Apple supports Apple Silicon in Xcode Cloud soon.

Forgot to include link to issue described above: https://github.com/pointfreeco/swift-snapshot-testing/issues/749