[Bug][Github][Pull Requests Metrics] Pull requests metrics missing data - project_pr_metrics table not populated

[caioq]

Search before asking

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

What happened

Since 2025-03-06, when using a GitHub connection with GitHub App and GraphQL, the table project_pr_metrics has not been receiving any data.
The pipeline completes with a success status, but no records are inserted into the table.

Blueprint configuration example:

{
  "plugin": "github_graphql",
  "subtasks": [
    "Collect Pull Requests",
    "Extract Pull Requests",
    "Collect Comments",
    "Extract Comments",
    "Collect PR Review Comments",
    "Extract PR Review Comments",
    "Collect Users",
    "Extract Users",
    "Enrich PR Issues",
    "Convert Repos",
    "Convert PR Commits",
    "Convert Pull Requests",
    "Convert PR Reviews",
    "Convert PR Labels",
    "Convert PR Issues",
    "Convert PR Comments",
    "Convert Reviews",
    "Convert Users"
  ],
  "options": {
    "connectionId": 1,
    "fullName": "XXX",
    "githubId": 999,
    "name": "XXX"
  }
},
{
  "plugin": "gitextractor",
  "subtasks": null,
  "options": {
    "connectionId": 1,
    "fullName": "XXX",
    "name": "XXX",
    "pluginName": "github",
    "proxy": "",
    "repoId": "github:GithubRepo:1:ZZZ",
    "url": "https://git:****************************************@github.com/XXX.git"
  }
}

What do you expect to happen

I expect the project_pr_metrics table to be populated with data when running the pipeline, as it was before March 6, 2025.

This data is crucial for tracking PR metrics, and the absence of records is impacting our ability to analyze GitHub contributions.

How to reproduce

1. Configure a GitHub App connection with GraphQL.
2. Run the pipeline with the configuration above.
3. Check the project_pr_metrics table in the database.

Expected: Data should be inserted into project_pr_metrics.

Anything else

• This issue occurs every time the pipeline runs since 2025-03-06.
• I tried executing Re-Transform, but this only made the problem worse. It seems that the behavior applied to previous pull requests as well, increasing the number of PRs without metrics.
• I also tested a new project running locally, and no records were inserted into the project_pr_metrics table.

Version

v1.0.1 and SHA: 8240c8d

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]

I found a similar closed issue that might be relevant to your problem: [Bug][Project] project_mapping is empty when only GitHub data is collected. This issue was resolved by a pull request that addressed the problem of no entities being specified, which led to using all entities enabled by default. The issue was closed on December 6, 2023. You can view the details of the issue here.

While this specific issue was related to the project_mapping table, the resolution might provide insights into potential configuration or default settings that could affect data insertion into tables like project_pr_metrics. It might be worth checking if similar configuration adjustments could resolve your issue.

To continue talking to Dosu, mention @dosu.

---

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