GitHub-backed projects
GitHub-backed workflows allow Miglify to inspect project structure and access Edge Function source code where available.
Why GitHub connection matters
Source code access improves Edge Function deployment readiness. Without it, Miglify may detect a function through Supabase but lack what it needs to deploy it.
GitHub OAuth repo picker
Miglify uses GitHub OAuth to let you select the specific repository backing your project. Only the repository you choose is used for analysis.
Repository analysis
Miglify inspects the repository for supported project structure, Edge Function directories, and required Secret names.
Edge Function source code access
When source code is available, Miglify can package and deploy functions automatically to the destination Supabase project.
Deployment readiness
- Function source code is present in the repository.
- Required Secrets are configured or ready to apply.
- Destination Supabase credentials and the required authorization are provided.
Permissions and safety
Only the repository you authorize is accessed. You can disconnect GitHub at any time from account settings.
Disconnecting GitHub
Remove the GitHub connection from your account settings when you no longer need it. Existing job history remains, but future analysis will not have source access.
Troubleshooting GitHub access
- Repository not appearing in the picker: confirm OAuth scopes and organization access.
- Missing functions: confirm they exist in the expected directory in the repo.
- Access errors: reconnect GitHub OAuth and retry analysis.