Creating a Pull Request using Actions (Fine Grained Token PAT) #131615
Replies: 1 comment
|
🕒 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! 💬 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Pull Request automation
Body
This may possibly be a bug report.
It seems that using fine grained tokens doesn't support creating a pull request for a fork to upstream. Example:

https://github.com/bsq-ports/Chroma/actions/runs/9867981598/job/27249620101
To explain my situation, my action forks a repository, makes a commit and then attempts to make a pull request on my behalf to the upstream repository of the fork. The fork and upstream are not the same as the workflow's repository.
Using a classic token with full repository permissions seems to work but I'm wondering if I can preferably use fine grained tokens.
My Github Action code creating the pull request
Previous discussions related confused me which is why I'm looking for clarity.
Thanks
On another note, I also attempted to use the workflow permissions syntax but it seems intentionally limited to avoid security issues for situations such as this.
Reference:
All reactions