You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GitHub integration branch functionality broken when using remotes with default auth.email.template.*.content_path values #2963
Describe the bug
When attempting to use a persistent branch with remotes values for auth.email.template.*.content_path in config.toml, the GitHub integration breaks on PRs with a Invalid config for (name): open (path): no such file or directory error.
To Reproduce
Create a monorepo with a Supabase config.toml in one package
In the config.toml, set values for auth.email.template.*.content_path. For example:
[auth.email.template.confirmation]
subject = "Confirm Your Signup"
content_path = "./supabase/templates/confirmation.html"
Set up a persistent branch via CLI
In the config.toml, add a remotes entry. For example:
changed the title [-]GitHub branchfunctionality broken when using `remotes` with default `auth.email.template.*.content_path` values[/-][+]GitHub integration branch functionality broken when using `remotes` with default `auth.email.template.*.content_path` values[/+]on Dec 10, 2024
Thanks for reporting this issue. It's apparently working only if supabase directory is at top level of your repo. I will push a fix for monorepo setups where supabase directory is nested somewhere.
Activity
[-]GitHub branchfunctionality broken when using `remotes` with default `auth.email.template.*.content_path` values[/-][+]GitHub integration branch functionality broken when using `remotes` with default `auth.email.template.*.content_path` values[/+]sweatybridge commentedon Dec 11, 2024
Thanks for reporting this issue. It's apparently working only if supabase directory is at top level of your repo. I will push a fix for monorepo setups where supabase directory is nested somewhere.