Add Google OAuth to the sign-in page
younglah added a "Sign in with Google" button to the login page using Supabase's OAuth flow, with an "or" divider above the existing email/password form. The same commit rebrands the footer to identify this as an internal Helinox deployment.
The new handleGoogleLogin handler calls supabase.auth.signInWithOAuth with provider: "google" and redirects to /assistant on completion. It's about 10 lines of actual logic. The Google icon is a hardcoded inline SVG with the four brand-color paths.
The footer change - "Helinox internal legal platform. Authorized users only." - is fork-specific and should not be pulled. But the OAuth wiring itself is self-contained and has no Helinox-specific dependencies.
One prerequisite: Google must be configured as an enabled provider in the Supabase project dashboard. The code calls the provider by name, and Supabase will return an error if Google OAuth isn't activated on that project. Nothing in the diff handles that case beyond surface-level error display.
The rest of the diff is reformatting. Collapsed JSX attributes, dropped the unused data destructure from signInWithPassword.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?