where to raise PR if the Issue is linked to other repo in the supabase

i am trying to work on this issue https://github.com/supabase/supabase/issues/39394 which on investigation i found is related to this repo https://github.com/supabase/auth how should i raise a file a new issue and link existing issue to that or raise a PR than link that
GitHub
Bug Report: missing destination name oauth_client_id in *models.Ses...
Description After a successful Google OAuth sign-in, the session is created correctly, but when Supabase attempts to refresh the session (/token endpoint with grant_type=refresh_token), the server ...
GitHub
GitHub - supabase/auth: A JWT based API for managing users and issu...
A JWT based API for managing users and issuing JWT tokens - supabase/auth
3 Replies
ihm40
ihm404d ago
I guess raise the pr in the repo you are changing and mention in the description that this is a fix for xxx issue/discussion on supabase That is my best guess but i'd check if there are any contributing docs that provide guidance
Vansh
VanshOP3d ago
okay thanks buddy
Kari S
Kari S2d ago
Any luck with the issue? I'm getting same error after unpause. Has Supabase rolled out updated Auth schema? Status page says some projects might be stuck: --- Oct 17, 2025 Project and branch lifecycle workflows affected in EU and APAC regions Resolved - We are no longer observing capacity issues with our cloud provider, and there have been no capacity related errors with new project creation, restores, restarts, or upgrades in the past 24 hours. Some projects remain stuck and require manual intervention. Our team is actively working through these requests. Oct 17, 15:17 UTC Update - We are currently experiencing capacity issues across all EU and APAC regions due to a surge in project creation requests. This is impacting the availability of Nano and Micro instance types. Larger compute sizes are not impacted. Note: Branches are deployed as Micro by default, so branching from larger compute sizes may be impacted. As a result, users may encounter errors when attempting the following operations on a Nano or Micro instance: - Project creation - Project restore - Project restart - Project resize - Unpausing projects - Database upgrade - Read replica creation - Branch creation We are continuously monitoring available capacity across all regions and will enable or disable project and branch lifecycle workflows (listed above) as needed based on current capacity. At this time, these workflows are enabled in all regions. Existing active projects in the region remain unaffected. Oct 16, 18:50 UTC

Did you find this page helpful?