@ashwaniYDV Thank you for reporting! There are some edge cases. One of your PR(let PR_1) is merged before PR_2, although PR_2 was created before PR_1. We will fix it soon.

@ashwaniYDV Thank you for reporting! There are some edge cases. One of your PR(let PR_1) is merged before PR_2, although PR_2 was created before PR_1. We will fix it soon.

This bug is still existing. Do you need a hand?

@lolimay Sure

Current workflow-

• lastMergedPR, lastOpenPR, lastIssue, which keeps track of the last created_at of corresponding data for a user of a given repo.
• Refresh will fetch all the repo of org -> fetch total_issue_count of marked repo -> check if there is the difference between the total_issue_count.
• If there is a difference, (let n be that difference) fetch last n issues and pulls, and update, if the stored created_at is less than fetched created_at

But storing only created_at lead to the bug which we are facing right now.
Proposed changes to fix the bug is here(pull #57).
Feel free to propose any approach which can fix the miscounting.