feat: include GitHub handles

[emlimlf]

In this PR

Added all the verified github handles to the members sorted and all the leaderboard pipes

Ticket

IN-974

---

Note

Medium Risk
Touches multiple Tinybird datasources/pipes and changes output schema types (string � array), which can break downstream consumers and requires backfill/migration validation.

Overview
Updates Tinybird schemas and pipes to return all verified GitHub usernames per member as githubHandleArray (Array(String)) instead of a single githubHandle string.

members_sorted_copy_pipe now aggregates verified GitHub usernames via groupArray from memberIdentities and denormalizes them into members_sorted; all leaderboard-related copy/query pipes and leaderboards_copy_ds are updated to select/emit githubHandleArray (using [] defaults for non-contributor leaderboards).

^{Written by Cursor Bugbot for commit 2c0362c. This will update automatically on new commits. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[gaspergrom]

keep just github one githubHandle property

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[emlimlf]

@gaspergrom I made it this way so that the frontend doesn't produce an error because of the change. Once this PR: linuxfoundation/insights#1685 is merged and deployed to prod, I can remove the other github handle property and just keep the array one.

[emlimlf]

Anyway, I've removed the old github handle property. But this must not be deployed and merge until the frontend PR has been merged and deployed to prod.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[cursor]

Missing deduplication produces duplicate GitHub handles in array

Low Severity

groupArray(value) collects all values without deduplication. The memberIdentities table's ReplacingMergeTree deduplicates by (integrationId, memberId, id), so after FINAL, the same GitHub username can still appear in multiple rows if it was discovered by different integrations (different integrationId or id). This produces duplicate entries like ['octocat', 'octocat'] in githubHandleArray. The previous argMax approach inherently returned a single value, so this is a regression. groupUniqArray would be more appropriate here.

 

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.