Missing access for the GITHUB_TOKEN for workflows #150597
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! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I am working on a GitHub action which synchronizes content from a template repository into decentral repositories. Within the github action we are using different tokens in order to make access to private repositories work. While carrying out a syncrhonization for workflow file I stumbled accross the issue that the permission for the GITHUB_TOKEN cannot be set for updating workflow file.
Error:
refusing to allow a GitHub App to create or update workflow
.github/workflows/pr.yamlwithout
workflowspermission
workflows cannot be set to write apparently and this is a limitation which I would like to have been fixed
https://docs.github.com.mcas.ms/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token#defining-access-for-the-github_token-permissions
permissions:
This is possible for "normal" GitHub actions on the permissions config. Why is this not possible for the default github_token?
Thanks for your help,
Alex
Beta Was this translation helpful? Give feedback.
All reactions