Duplicate PR collaboration activities

[rithviknishad]

Currently activities such as "PR collaboration" may get duplicated when the default branch gets merged to another branch such as production/staging. This misjudges collaboration activities.

Proposed Solution

• Exclude PR activities where the base branch is the non-default branch of the repository.

cc: @bodhish

[VAIBHAVSING]

/assign

[VAIBHAVSING]

@rithviknishad can you describe this issue in berif

[rithviknishad]

PR collaboration events should be tracked only for if the PR's base branch is the repository default branch

leaderboard/scraper/src/github-scraper/parseEvents.ts

Lines 113 to 120 in 6e38a43

	appendEvent(user, {
	type: "pr_collaborated",
	title: `${event.repo.name}#${event.payload.pull_request.number}`,
	time: eventTime.toISOString(),
	link: event.payload.pull_request.html_url,
	text: event.payload.pull_request.title,
	collaborated_with: [...othersArray],
	});

[VAIBHAVSING]

@rithviknishad hello sir ,
I will not able to run scrapper can you assign to another person please.

[rithviknishad]

Are you facing any difficulties running the scraper?

[VAIBHAVSING]

@rithviknishad i will not able run scrapper after pasting github token in that

[rithviknishad]

here's the command to run the scraper

GITHUB_TOKEN=$(gh auth token) pnpm dev ohcnetwork ../data-repo/data/github

[VAIBHAVSING]

@rithviknishad can i completely ignore merge request from stagging or production branch or only ignore in above provided code at addcollaboration

[rithviknishad]

Didn't understand that, but whatever that was done in the PR is right.