这是indexloc提供的服务,不要输入任何密码
Skip to content

Fix resyntax permissions issue #1253

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

Merged
merged 1 commit into from
Jul 3, 2022
Merged

Fix resyntax permissions issue #1253

merged 1 commit into from
Jul 3, 2022

Conversation

jackfirth
Copy link
Contributor

The current Resyntax workflow runs on pull_request, which gives it a github token with read-only access when run on pull requests from forks. Using pull_request_target instead gives it a read-write token and allows the action to submit pull request reviews for pull requests from forks.

The current Resyntax workflow runs on `pull_request`, which gives it a github token with **read-only** access when run on pull requests from forks. Using `pull_request_target` instead gives it a read-write token and allows the action to submit pull request reviews for pull requests from forks.
@samth samth merged commit f534722 into master Jul 3, 2022
@jackfirth
Copy link
Contributor Author

Update: this didn't work. A better strategy is outlined here. I'll give that approach a try next.

jackfirth added a commit to jackfirth/resyntax that referenced this pull request Jul 7, 2022
This is in preparation for moving the pull request submission logic into a separate workflow, instead of performing that API call in resyntax directly. See racket/typed-racket#1253 for more context.
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 this pull request may close these issues.

2 participants