Skip to content

Fix TS_GITHUB_BOT_AUTH access permission #1079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
saschanaz opened this issue Jul 31, 2021 · 3 comments · Fixed by #1127
Closed

Fix TS_GITHUB_BOT_AUTH access permission #1079

saschanaz opened this issue Jul 31, 2021 · 3 comments · Fixed by #1127

Comments

@saschanaz
Copy link
Contributor

saschanaz commented Jul 31, 2021

It needs public_repo read access. @orta

@saschanaz
Copy link
Contributor Author

@orta Adding read access should be no-brainer, what's blocking it? 😬

@orta
Copy link
Contributor

orta commented Aug 30, 2021

I think the workflow is probably misconfigured, the token does have read access but it doesn't have write access to this repo:

Pushing pull request branch to 'origin/update-core-deps'
  /usr/bin/git push --force-with-lease origin HEAD:refs/heads/update-core-deps
  remote: Permission to microsoft/TypeScript-DOM-lib-generator.git denied to typescript-bot.
  fatal: unable to access 'https://github.com/microsoft/TypeScript-DOM-lib-generator/': The requested URL returned error: 403

logs

Maybe there's a setting for declaring what repo to send a fork from?

@saschanaz
Copy link
Contributor Author

Hmm, it seems public_repo automatically allowed write access for me since the token was from the repo owner account. Not if it's from the bot account, for sure. Can the bot have a fork?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants