Replies: 3 comments
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
I'm running into the same issue, here's an example Still looking for a workaround as well |
Beta Was this translation helpful? Give feedback.
-
@redocecin I've re-created this as a bug, since this discussion got closed by the stalebot: https://github.com/orgs/community/discussions/133700 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I need to implement a workflow that executes Playwright tests immediately after a successful deployment of a PR to a staging environment. The current structure of my workflow file is as follows:
This workflow functions as expected when I initiate a PR from a branch within the primary repository. However, when I initiate a PR from a forked repository, I encounter the following error message:
Is this behavior intentional? If yes, can you please provide me with an alternative approach?
Beta Was this translation helpful? Give feedback.
All reactions