This PR adds dynamic expo builds for PR's
When a PR is made we first run expo update to publish an expo-go version of the app, we do this first because expo-go updates are quick fast and this allows us to continue with our iterative process.
We then do two things, expo-build AND another expo-update. We do both because we know that expo-update does an OTA for the expo-build app in this way we can continually test that the two together are still working. Again, we do this separately so that we do not slow down the dev process, considering that expo-build is much slower.
In order to build the review app we also make a temporary change to the eas.json config, here we create a new entry in the config that dynamically creates a new channel with our PR number and a build profile for that build number. The reason we do not use the statically defined profile is that our builds are also tied to to channels, that means when we run this command we would be updating any other review app out there.
Checklist
[ ] Todo 1
[ ] Todo 2
[ ] Todo 3
How to test
Add user steps to achieve desired functionality for this feature.
What this does
This PR adds dynamic expo builds for PR's When a PR is made we first run expo update to publish an expo-go version of the app, we do this first because expo-go updates are quick fast and this allows us to continue with our iterative process. We then do two things, expo-build AND another expo-update. We do both because we know that expo-update does an OTA for the expo-build app in this way we can continually test that the two together are still working. Again, we do this separately so that we do not slow down the dev process, considering that expo-build is much slower.
In order to build the review app we also make a temporary change to the eas.json config, here we create a new entry in the config that dynamically creates a new channel with our PR number and a build profile for that build number. The reason we do not use the statically defined profile is that our builds are also tied to to channels, that means when we run this command we would be updating any other review app out there.
Checklist
How to test
Add user steps to achieve desired functionality for this feature.