[slf4j-dev] [JIRA] Updates for SLF4J-553: Add GitHub token permissions for GitHub Actions workflow
QOS.CH (JIRA)
noreply-jira at qos.ch
Thu Jul 21 16:23:00 CEST 2022
SLF4J / SLF4J-553 [Resolved]
Add GitHub token permissions for GitHub Actions workflow
==============================
Here's what changed in this issue in the last few minutes.
There is 1 comment.
View or comment on issue using this link
https://jira.qos.ch/browse/SLF4J-553
==============================
1 comment
------------------------------
Varun Sharma on 21/Jul/22 4:10 PM
I think it has to do with the order of events. GitHub token permissions were introduced after developers had already started using the token, so having "contents: read" as default later on would have broken some existing workflows that needed higher permissions and had not yet set them explicitly.
You can set "contents: read" as default for your repo and org using the UI: https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/
==============================
This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)
More information about the slf4j-dev
mailing list