Conversation
|
Hi! 👋 To ensure a smooth review process, it is recommended to trigger a build (or an update if no native changes have been made since the last build). You can do so by applying the appropriate label based on your needs: • 🏗️ 🍏 iOS Build: Select Note The update is managed by a custom GitHub action, while the build actions are handled directly via EAS integration. Once you apply the respective label, the appropriate workflow will be triggered automatically. You can monitor the progress in the Actions tab. Warning If you push new commits to your PR branch after selecting a build label, a new build will be triggered automatically. It is advisable to remove the label once applied and reapply it if necessary; you will likely need to trigger an update instead of a fresh build. Important After merging changes into the dev branch, a build will automatically be triggered for both platform using the dev profile. Therefore, there is no need to manually initiate a build after merging to the dev branch. Additionally, builds will automatically trigger when promoting changes to dev, test and prod. For the prod branch, the build will also be automatically submitted to the app stores. For more information, refer to the PR Reviews Guide. |
ShootingStar91
left a comment
There was a problem hiding this comment.
Looks like good changes to me, and seems to work fine.
✨ What has changed?
This PR does the following:
🔍 How to verify?
Launch a build (from that branch) and check that the notification in #builds Slack channel.