Fixes #503; Correct event owner for pr_merged events
#512
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
rithviknishad
requested review from
bodhish,
shivankacker,
khavinshankar and
sainak
rithviknishad
changed the title
pr_merged eventspr_merged events
khavinshankar
approved these changes
Sep 4, 2024
shivankacker
approved these changes
Sep 4, 2024
bodhish
approved these changes
Sep 4, 2024
sainak
approved these changes
Sep 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pr_mergedevents #512pr_mergedevents was using the event actor (in this case the one who merged the PR). However, in leaderboardpr_mergedevents are associated to the PR authors for incentivizing the contributor.Regression from recent scraper refactor from python to typescript