You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the expo/expo-github-action with the preview command in GitHub Actions. This setup is necessary for securely handling sensitive tokens like EXPO_TOKEN, especially for external contributors. However:
Using pull_request event instead results in external contributors not having access to EXPO_TOKEN, causing the error: "Skipped authentication: 'token' not provided."
We want to set up an action that automatically comments on pull requests with preview links when contributors open a PR. This would allow for quick review by maintainers.
Is there a better way to achieve our goal of automatically creating and commenting Expo previews on pull requests, while maintaining security for external contributions? We're open to alternative approaches or configurations that might solve this issue.
The text was updated successfully, but these errors were encountered:
IZUMI-Zu
changed the title
Expo Preview Action Fails with pull_request_target Event
Expo Preview Action Fails with pull_request Event
Aug 1, 2024
Topic and Issue
When using the
expo/expo-github-action
with the preview command in GitHub Actions. This setup is necessary for securely handling sensitive tokens likeEXPO_TOKEN
, especially for external contributors. However:pull_request
event instead results in external contributors not having access toEXPO_TOKEN
, causing the error: "Skipped authentication: 'token' not provided."My setup is basically the same as the example:
Motivation
We want to set up an action that automatically comments on pull requests with preview links when contributors open a PR. This would allow for quick review by maintainers.
Is there a better way to achieve our goal of automatically creating and commenting Expo previews on pull requests, while maintaining security for external contributions? We're open to alternative approaches or configurations that might solve this issue.
The text was updated successfully, but these errors were encountered: