Push access rights for GH_TOKEN for a fork when "Allow edits from maintainers" is active

[koppor]

Select Topic Area

Question

Body

I run a code-reformatter action which automatically commits changes (GitHub Prettier Action). When a push to a fork should happen, I get following error message:

Author: koppor <[email protected]>
961 files changed, 118393 insertions(+), 49535 deletions(-)
remote: Permission to koppor/jabref.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/koppor/jabref/': The requested URL returned error: 403

When creating the PR, the checkmark "Allow edits and access to secrets by maintainers" was set.

I think, "github-actions[bot]" should also be granted these rights. It has write access to the target repo, thus it should also have write access to the source repo.

---

Documentation on the "Allow edits from maintainers" feature: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

My wish: Is it possible to grant GH_TOKEN write access to the fork if "Allow edits from maintainers" is active.

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[koppor]

I did not provide a MWE. I also seem to be the only one having this issue. Thus, closing it.

[HannesWell]

I faced the exact same problem, when setting up a workflow that should push an extra commit with missing changes to the branch of a PR in a fork. Therefore I would be very interested in a solution too.

Maybe one solution would be to use a personal access token (PAT) issued for your own account or a separate bot account (if available) and to the changes with that PAT as for example described in:
https://michaelheap.com/ultimate-guide-github-actions-authentication/