Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: publish preview url only for the base repo prs #313

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

vasyl-ivanchuk
Copy link
Collaborator

What ❔

Publish preview url only for the base repo PRs.

Why ❔

Even though pull-requests: write permissions are specified for the Build and Test App GitHub workflow, forked PRs are executed under pull-requests: read permissions. This causes the Publish preview URL action to fail, as it attempts to add a comment to the PR. Using the pull_request_target event instead of pull_request is not an option, as the workflow builds and runs code from the pull request context. To resolve this, the Publish preview URL action was modified to run only for base repository PRs. This should not be a problem for the forked PRs, as the URL is still output to the GitHub Action logs.

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).

Copy link

API E2E Test Results

207 tests   207 ✅  19s ⏱️
 14 suites    0 💤
  1 files      0 ❌

Results for commit 1c70d1f.

Copy link

Unit Test Results

    4 files    263 suites   11m 21s ⏱️
2 124 tests 2 123 ✅ 1 💤 0 ❌
2 336 runs  2 335 ✅ 1 💤 0 ❌

Results for commit 1c70d1f.

Copy link

Visit the preview URL for this PR:
https://staging-scan-v2--pr-313-r0hs4sol.web.app

@popzxc popzxc merged commit dc26198 into main Nov 11, 2024
23 checks passed
@popzxc popzxc deleted the fix-gh-workflow-for-fork-prs branch November 11, 2024 06:00
Copy link

🎉 This PR is included in version 2.50.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants