[Bug][GitHub] merged_date,closed_date not updated when Pull Request is reopened

[konck2]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Syncing data in Devlake doesn't update merged_date and closed_date from pull_requests table when pull request has been closed -> reopened -> merged.

What do you expect to happen

merged_date and closed_date to be updated when Devlake sync job runs.

How to reproduce

1. Create PR within GitHub
2. Close it without merging
3. Run Devlake sync job
4. Reopen PR
5. Merge it
6. Run Devlake sync job

Anything else

pull_request table entry within lake database (MySQL):

updated_at	created_date	merged_date	closed_date
2024-12-16 00:20:36.776	2024-11-26 13:32:32.000	NULL	2024-11-27 08:04:46.000

GitHub API entry:
"created_at": "2024-11-26T13:32:32Z",
"updated_at": "2024-12-03T08:50:29Z",
"closed_at": "2024-12-03T08:50:27Z",
"merged_at": "2024-12-03T08:50:27Z",

Version

1.0.2-beta4

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

Hey @konck2! 👋 I'm here to help you with any bugs, questions, or contributions you have for Devlake. I'm like a bot with a knack for solving tech puzzles.

A similar issue was previously reported and closed: [Bug][Github] Pull Requests not being updated](#7851). This issue was resolved by a pull request that fixed the GitHub GraphQL collectors to refetch data in incremental mode. You might want to check if this fix is applicable to your situation or if there are any updates related to this in the latest version of DevLake ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[klesh]

Known issue, won't be fixed.
This is a side-effect of #7878