Replies: 2 comments
-
|
Anyone. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Workflow Configuration
Discussion Details
Hi!
Our project requires a CI to succeed for a PR to be merged. We, as collaborators, cannot merge forcefully. The problem here is that the CI requires 2 secrets (from the base branch) and code from the head branch (the PR's changes). We tried using the
pull_requestscope first, but it failed as the secrets were not available in the head branch. After changing topull_request_target, we can't test the commits in PRs. Is there any good way to do this?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions