Add GitHub issue data and connect with user profiles

[SahilDhillon21]

Fixes #3265

Extended the handle_pull_request_event function to also add the pull request data to the database

Could you please verify if the webhook is working? Since on the site the pull request badges are not being assigned automatically despite having added the GitHub URL to the profile

[DonnieBLT]

This looks great thank you! Can you please make a model GitHubIssues and store them there instead? Also check the first pr badge logic to only trigger on the first. Also please add a count in the profile.

[SahilDhillon21]

This looks great thank you! Can you please make a model GitHubIssues and store them there instead? Also check the first pr badge logic to only trigger on the first. Also please add a count in the profile.

Did you mean GithubPullRequests instead of issues, or do we want to store them both? Also, in that case, would it be better to use a scheduled command to fetch pr data regularly or the webhook only?

[DonnieBLT]

This looks great thank you! Can you please make a model GitHubIssues and store them there instead? Also check the first pr badge logic to only trigger on the first. Also please add a count in the profile.

Did you mean GithubPullRequests instead of issues, or do we want to store them both? Also, in that case, would it be better to use a scheduled command to fetch pr data regularly or the webhook only?

GitHub issues and pull requests are the same structure in their back end. We want to have GitHub issues along with pull requests so I think we could use one table.

[DonnieBLT]

I also think it will be good to have them be 1 line each so we can see many at one time, and have the counts up top merged, open, closed and rank compare to others merged pull requests

[DonnieBLT]

And group by organization / repository

[SahilDhillon21]

Understood!

[DonnieBLT]

Thank you!

[SahilDhillon21]

In progress

[SahilDhillon21]

In the GitHubIssue model, do we intend to store issue data of all existing repositories in the database
Or should we follow a user-centric approach where we fetch pull request data of only registered users who have added github_url in their profiles?

[DonnieBLT]

github_url sounds good!

[SahilDhillon21]

Overall look:

Summary

1. Updated UI for PR list, grouped by repo
2. Management command to fetch and update PR data from GitHub API
3. GitHubIssue model to store issue details
4. Added logic to rank users based on merged PRs and store contribution ranks.

@DonnieBLT @tsu-ki please take a look

[tsu-ki]

Overall look:

Summary

1. Updated UI for PR list, grouped by repo
2. Management command to fetch and update PR data from GitHub API
3. GitHubIssue model to store issue details
4. Added logic to rank users based on merged PRs and store contribution ranks.

@DonnieBLT @tsu-ki please take a look

looks amazing, great work man! Just a small suggestion, rather than displaying PRs from all repos, can we add a dropdown list and add repos to that list, so user can select which repo they want to view.
I made this suggestion because, I'll be adding the PR review section below this, and i'm unsure if it would fit within the page layout or not.