fails because one of those updates was apparently already applied on the remote - a quick check confirms that they changes are there.
What am I now supposed to do to rectify this? Is there some way to mark this migration file as applied on the remote? I can't just remove the migration file, as I need it locally to keep parity with remote.
I've taken over this project and the original devs are no longer available. I'm not very experienced with supabase (or dbs in general).
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.