Add support for tracking commits pushed to branch (core)

[rajku-dev]

Fixes #373

• enable pushed_commits tracking for core team members with direct push access to org
• enable pushed_commits tracking for non-core team contributors through forked repositories (Add support for tracking commits pushed to branch (Forked) #602)

[netlify]

👷 Deploy request for leaderboard-develop pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	1db1d86

[rajku-dev]

How can i test the scraper for debugging? i can't run it on local machine?
@rithviknishad

[rajku-dev]

There were two directions for each fetched Fork

1. Fetch all its events and filter the PushEvent (REST event endpoint)
2. Fetch all its branches and get their commit history (GraphQL)

i went with the second one for now.

[rithviknishad]

Not a fan of N+1 approach. If this was deployed for a much bigger github org, which has too many forks, fetching commit history of each fork's branches might go off the limits pretty quickly.

Let's do a 2 part PR. Let's first get the org's repo commits tracked first. We can figure out something for the fork's. We only ideally care about commits pushed directly to default branch and commits pushed to PR branches alone.

[rajku-dev]

Not a fan of N+1 approach. If this was deployed for a much bigger github org, which has too many forks, fetching commit history of each fork's branches might go off the limits pretty quickly.

Let's do a 2 part PR. Let's first get the org's repo commits tracked first. We can figure out something for the fork's. We only ideally care about commits pushed directly to default branch and commits pushed to PR branches alone.

I do agree with you, Please check this out #602 (comment)