-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lift to upstream ResearchKit 2.2.15 #14
Conversation
…_bump Point ResearchKit.podspec to 2.1.0
- Fixed `ORKHealthKitQuantityTypeAnswerFormat`issues - Improved `ORKReviewStep` initialization - Introduced a new property called `shouldAutomaticallyAdjustImageTintColor` on `ORKStep` to automatically adopt dark mode version of an image - Added `ORKSESQuestionResult` to Table View Providers - ORKCatalog Improvements - ORKImageSelectionView improvements - Bumped version to 2.2.12
- Various ORKTextChoiceOther and ORKChoiceOtherViewCell improvements - Bumped version to 2.2.15 - Bumped Cocoapod version to 2.2.15
Various ORKTextChoiceOther and ORKChoiceOtherViewCell improvements Bumped version to 2.2.15 Bumped Cocoapod version to 2.2.15
@PSchmiedmayer Please also adjust the merge checks of the repo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for updating this to the latest version of the upstream ResearchKit repo! 👍
@philippzagar I adjusted the merge checks. One thing that I was thinking was maybe adding a GitHub Note (in the formatting we have in some READMEs of our other repos) that notes how this repo is different from the main RK repo? I could see this right before the badges. Maybe something like:
Feel free to add and adapt this as you want to; serves more as a placeholder and idea. |
# Enable C++ interop archiving ## ♻️ Current situation & Problem Currently, the reusable workflow doesn't enable compilation with active Swift / C++ interop mode. ## ⚙️ Release Notes - Enable the creation of XCArchives with active Swift / C++ interop mode via workflow parameter. ## 📚 Documentation -- ## ✅ Testing Tested with the ResearchKit repo in StanfordBDHG/ResearchKit#14 ### Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md).
Great idea @PSchmiedmayer, I think we have enough diff to upstream that this definitely makes sense! |
@PSchmiedmayer You also need to merge the PR as not all commits from upstream were signed. |
Thank you @philippzagar; I will merge the PR 👍 |
Lift to upstream ResearchKit 2.2.15
♻️ Current situation & Problem
The current used ResearchKit version of our fork is 2.2.12, which is not up to date with the published ResearchKit in 2.2.15.
Furthermore, as described in #13, we currently don't validate within the CI if ResearchKit compiles with active Swift / C++ interop.
⚙️ Release Notes
📚 Documentation
Documented CI approach
✅ Testing
Built code (in C++ interop mode) via CI pipeline
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: