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

docs: rs-semver-checks should be ran under pull_request_target #22

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

aborgna-q
Copy link
Collaborator

Closes #20

@aborgna-q aborgna-q requested a review from a team as a code owner November 15, 2024 14:13
@aborgna-q aborgna-q requested a review from croyzor November 15, 2024 14:13
@aborgna-q aborgna-q added this pull request to the merge queue Nov 15, 2024
Merged via the queue into main with commit b1d1dcd Nov 15, 2024
1 check passed
@aborgna-q aborgna-q deleted the ab/semver-checks-trigger branch November 15, 2024 14:53
github-merge-queue bot pushed a commit that referenced this pull request Nov 27, 2024
#22 changed the recommended trigger for the semver checks action to
`pull_request_target`, but inside the action we were still checking for
`pull_request` targets explicitly so the comments never got posted.

Note that for both events the payload is still called `pull_request`, so
there's no need to change the rest of the code.

https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#pull_request_target
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.

(rs-semver-checks): Dependabot-triggered PRs cannot access repo secrets
2 participants