HarshCasper / HarshCasper/Rotten-Scripts

Report: Present a report on the state of Pull Requests

Open
#758 9 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue GSSOC21 Hard Python Up-For-Grab Urgent
Dominant language
Python
Stars
1.5k
Forks
497
PR merge metrics
No merged PRs in 30d

Description

## Description

Up till now, nearly 65+ Contributors have contributed to Rotten Scripts with more than 400+ Pull Requests created and 350+ Issues created. I want to better understand on how easy has the contributions been for the Contributors.

Since the Project has been a part of many Open-Source Programs, I need to understand how many PRs have been merged and how many PRs were closed. You can also scrap the comments and use some NLP techniques, to determine the most common reasons why PRs were closed and whether they were done by me or the contributor themselves.

I'm open to new ideas, but this is what the workflow should look like:

- Scrap PRs from the Project
- Store all of them in a neat CSV format
- Use your Data Visualization and NLP skills in churning out necessary insights
- Find the most common reasons on why PRs are closed and by whom
- Check out other stats like Average time for every PR to be reviewed, the most active maintainer and more
- Present all of these findings in the Discussions Tabs

The whole thing should be easily reproducible so please make a PR over the `Others` so that we can run the check and churn out stats every couple of months.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.