Skip to content

fix: use pull_request_target event as the trigger of PR triaging agent #2244

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 30, 2025

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Jul 29, 2025

fix: use pull_request_target event as the trigger of PR triaging agent

GitHub workflows triggered by pull_request events from forked repositories do not have access to secrets by default due to security considerations.

@copybara-service copybara-service bot added the google-contributor [Bot] This PR is created by Google label Jul 29, 2025
@copybara-service copybara-service bot force-pushed the copybara/788607120 branch from e1e143e to e913b53 Compare July 30, 2025 20:01
GitHub workflows triggered by `pull_request` events from forked repositories do not have access to secrets by default due to security considerations.

PiperOrigin-RevId: 789011890
@copybara-service copybara-service bot force-pushed the copybara/788607120 branch from e913b53 to 3be1bb3 Compare July 30, 2025 20:05
@copybara-service copybara-service bot merged commit 3be1bb3 into main Jul 30, 2025
@copybara-service copybara-service bot deleted the copybara/788607120 branch July 30, 2025 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
google-contributor [Bot] This PR is created by Google
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant