Replies: 2 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 believe cases 2 and 3 are not actually from forks: both branches are in the upstream repository. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hello,
I am seeking clarification on the permissions associated with
pull_request
events in Github Actions, specifically regarding write permissions. The documentation states:Link to documentation
However another section of the documentation suggests otherwise:
Link to documentation
Based on this information and this blog, I inferred that only Dependabot has special privileges to receive write permission when creating a pull request from a forked repository. To test this hypothesis, I conducted the following experiment:
First, I created a YAML file that enables auto-merging pull requests:
Then, I created the following pull requests:
The result for case 3 is confusing to me because I assumed that only pull requests triggered by Dependabot are treated as special. Despite being from forked repository, the pull request by Renovate was granted write permission.
Could you provide insights into this behavior? Thank you.
Beta Was this translation helpful? Give feedback.
All reactions