Skip to content

Fix GitHub Actions#43

Merged
JulienTexier merged 18 commits intodevfrom
chore/fix-github-actions
Jun 6, 2025
Merged

Fix GitHub Actions#43
JulienTexier merged 18 commits intodevfrom
chore/fix-github-actions

Conversation

@JulienTexier
Copy link
Collaborator

@JulienTexier JulienTexier commented May 20, 2025

✨ What has changed?

This PR does the following:

  • Removes Auto Labelling GitHub Action. This action was not working properly and caused more issues than benefits
  • Adds documentation check on PR Template
  • Fixes EAS Build & EAS Update GitHub Actions
  • Fixes the environment name after convention change in previous PR in GitHub Actions & custom scripts.
  • Updates documentation about client emailing from the EAS Build action.

🔍 How to verify?

Launch a build (from that branch) and check that the notification in #builds Slack channel.

@github-actions
Copy link

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 eas-build-ios:dev to trigger a build for iOS
• 🏗️ 🤖 Android Build: Select eas-build-android:dev to trigger a build for Android
• 🏗️ 📲 All Platforms Build: Select eas-build-all:dev to trigger builds for both platforms
• 🌐 EAS Update: Select eas-update to trigger an update (automatically for both platforms)

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.

@JulienTexier JulienTexier added the ci/cd A label for changes to the CI/CD pipeline, including updates to automation scripts, GitHub Actions.. label Jun 3, 2025
@JulienTexier JulienTexier requested a review from Temzasse June 3, 2025 08:55
@JulienTexier JulienTexier marked this pull request as ready for review June 3, 2025 08:57
Copy link
Collaborator

@ShootingStar91 ShootingStar91 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like good changes to me, and seems to work fine.

@JulienTexier JulienTexier merged commit acf9da3 into dev Jun 6, 2025
4 checks passed
@JulienTexier JulienTexier deleted the chore/fix-github-actions branch June 6, 2025 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/cd A label for changes to the CI/CD pipeline, including updates to automation scripts, GitHub Actions..

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants