I'm having a problem with GitHub integration using supabase. It seems that when I commit to my dev branch, the deployment is triggered and completes successfully according to GitHub, but when I check Supabase, I see no changes. I've been trying to figure out why it's not working.

I even created a new branch to see if the problem was with dev, but it still doesn't update the new branch. It's even stranger that the new branch (like dev) pulled a commit from a few days ago instead of the latest one. The problem has been around for a long time and that simply wasn't updating the code, but a few days ago, miraculously, it updated a commit (which supabase mark as 502 Bad Gateway) and has remained stuck there until now, the commit wasnt special, it was updating only simple code without any config for github or supabase.

According to the dev logs in supabase, 'No change found in Function' and it doesn't update, but there are clearly changes.

2026/01/21 19:05:47 INFO Downloading function... slug=survey-to-blueprint-etl
No change found in Function: survey-to-blueprint-etl

Another thing is that I have this in the logs:

• This is extracting migrations from two different databases; when it was working, there was only one extraction.

• it is 'pulling a project config from main env', that log does not appear before the error

2026/01/21 19:05:44 INFO Cloning git repo... git_ref=develop
2026/01/21 19:05:45 INFO Pulling migrations from database... host=[xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx]:5432
2026/01/21 19:05:45 INFO Pulling migrations from database... host=[yyyy:yyyy:yyyy:yyyy:yyyy:yyyy:yyyy:yyyy]:5432
2026/01/21 19:05:46 INFO Pulling project config... project_ref=project_ref_to_MAIN
2026/01/21 19:05:46 INFO Checking service health... project_ref=correct_ref_to_DEV

I'm not sure if that last bit of data is relevant, but it's strange that the problem appeared when it started appearing.

If it helps, here's my config.toml

project_id = ref_to_dev

[functions.survey-to-blueprint-etl]
verify_jwt = false

Interesting facts:

• Some people use Lovable for commits; deployment works fine when the commit is made for Lovable. Previously, deployment worked fine with any commit.

• It used to happen that the dev and main branches would get swapped and deploy to the other, but that fixed itself (now it simply doesn't deploy, haha)