write permission check using github API about keepalive-workflow HOT 6 CLOSED

@lgmorand, it looks like there is an even simpler way to detect branch protection just by using process.env.GITHUB_REF_PROTECTED === 'true'

But this won't still fix the token permission issue though. We still need to use the token permission API to determine if the token provided has write access to the repo. But adding branch protection check is the first step.

from keepalive-workflow.

indeed. Branch protection is something you can't do much. but helping to understand that token doesn't have enough rights could be useful

from keepalive-workflow.

it looks like github api do not support it right now:

curl -sS -f -H "Authorization: token <token>" https://api.github.com/repos/example-user/example-repo  | jq .permissions
{
  "admin": false,
  "maintain": false,
  "push": false,
  "triage": false,
  "pull": false
}

This is the response we always get.

there are other users who also have same problem: https://github.com/orgs/community/discussions/25259

Created new bug report here: https://github.com/orgs/community/discussions/73397

from keepalive-workflow.

maybe you could just check the current branch status because token scope won't help in any case I think

https://api.github.com/repos/OWNER/REPO/branches/BRANCH/protection

It would report if the current branch is protected or not. if yes, add a warning/exit

from keepalive-workflow.

@lgmorand thanks a lot for the suggestion. This looks like a great option. Will give it a try. Never knew that this API existed before 😄

from keepalive-workflow.