GSSoC-approved PRs not appearing after DevTrack repository transfer

[bhavyajain0810]

Hi @Priyanshu-byte-coder,

Four of my approved and merged DevTrack PRs are still not appearing on either my official GSSoC profile or the community PR tracker, even though it has been more than a week:

• feat(dashboard): add customizable widget layout #2006
• fix: surface GitHub API rate limit errors on dashboard #2012
• test: add Playwright visual regression coverage #2034
• feat: add shareable links for individual goals #2037

All four PRs were assigned to me, merged, and have the gssoc:approved label.

It appears that GSSoC may still have DevTrack registered under the previous repository path, Priyanshu-byte-coder/devtrack, while the repository is now under Umbrella-io/devtrack.

Could you please confirm whether the repository transfer was reported to the GSSoC team and whether the registered repository URL can be updated? This may be preventing PRs merged after the transfer from being tracked.

GitHub username: bhavyajain0810

Thank you.

[Priyanshu-byte-coder]

All four PRs (#2006, #2012, #2034, #2037) already have gssoc:approved and are properly labeled on our end.

The tracking issue is on GSSoC's side — they likely still have DevTrack registered under Priyanshu-byte-coder/devtrack instead of Umbrella-io/devtrack. We've reached out to the GSSoC team to update the registered repository URL. Once they update it, your PRs should reflect on your profile.

Will follow up here once we hear back.

[sumitkumar2374]

If the repository was transferred to a new organization, it's possible that the GSSoC tracker is still pointing to the old repository path. Hopefully, the maintainer can confirm whether the new repository has been registered with the GSSoC team. Once updated, the missing PRs should be tracked correctly if they meet the program requirements.

[Priyanshu-byte-coder]

the ownership of repo was transfered back to the original one, so rule out that for now.