Skip to content
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

[Dev][CI] autotune failing to push to PR branches? #38315

Open
jonkeane opened this issue Oct 17, 2023 · 2 comments · May be fixed by #38523
Open

[Dev][CI] autotune failing to push to PR branches? #38315

jonkeane opened this issue Oct 17, 2023 · 2 comments · May be fixed by #38523

Comments

@jonkeane
Copy link
Member

Describe the bug, including details regarding any error messages, version, and platform.

I just tried to autotune and generate docs, but that failed with:

Run r-lib/actions/pr-push@v2
Collecting information about PR #38258...
git push ***github.com/Divyansh200102/arrow.git -q HEAD:open_dataset(format-=-json-)-not-documented
remote: Permission to Divyansh200102/arrow.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/Divyansh200102/arrow.git/': The requested URL returned error: 403
Error: The process 'git' failed with exit code 128

It looks like that PR has permissions for maintainers to push to it — so maybe this is an issue that our github bot user no longer has the correct scope? I also was able to push to this branch personally, so I suspect it's something wrong with the actions runner permissions scope.

cc @assignUser since you know lots about github (actions) permissions

Component(s)

Continuous Integration, Developer Tools

@jonkeane
Copy link
Member Author

I've also looked to see if the r-libs/actions/pr-push has been updated and it's still on v2

r-lib/actions#563 (comment) might be related (though which permissions were at issue weren't described)

@assignUser
Copy link
Member

Yeah this is probably due to a change to the default permission + this workflow being rarely used. I can have a look

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

Successfully merging a pull request may close this issue.

3 participants