Fix the problem about stale pr table accuracy

ti-community-infra / devstats

TiDB's community tool for analyzing and graphing developer contributions.

Apache License 2.0

2 stars 2 forks source link

Fix the problem about stale pr table accuracy #85

Closed Mini256 closed 3 years ago

Mini256 commented 3 years ago

Bug Report

[x] I have searched the issues of this repository and believe that this is not a duplicate.

What is expected?

The merged PR should not be judged as Stale PR.

What is actually happening?

There are some PRs that are mistaken to be Stale PR. A part of them is because the event data of ghacrhive has been lost in the past.

Related dashboard：

stale-pr-table
stale-prs-by-sig

Mini256 commented 3 years ago

Maybe we can use hybrid data which combined with GhArchive and GitHub API.

cc: @tisonkun

Mini256 commented 3 years ago

I used the sync_issues program to patch some of the missing issue statuses in the past through the GitHub API.

The number of Stale PR has dropped significantly:

The sync_issues tool will complete a fake event of type sync, and provide the status of the current issue (including state, assignee, labels...) through this event. The actor of these events is named devstats-sync.

Mini256 commented 3 years ago

Done.