Upload screenshots to Emerge in addition to pushing them to the paywall validation repo. #5351
Conversation
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
…ll validation repo.
1 build had no size change
RevenueCat 1.0 (1)
|
📸 Snapshot Test216 unchanged
🛸 Powered by Emerge Tools |
Now that emerge is part of our gemfile, it requires Ruby >= 3.2.0.
joshdholtz
approved these changes
Jul 8, 2025
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.
Motivation
This will give us a nice way to validate changes to the paywall validation screenshots using Emerge and quickly identify regressions. We are already doing this for Android.
Description
After generating the screenshots and before pushing them to the paywall rendering validation repo, take the folder and upload it to Emerge using the emerge command line tool.