Deploy Migrations to Staging workflow always fails in forked repositories

[mnixo]

Expected Behavior

After forking the repository, a contributor expects to find the fork just as stable (at least) as the original repository.

Current Behavior

The Deploy Migrations to Staging workflow fails every time dev is updated. Example run.

Any other notes

This is caused by the missing secrets values that are necessary to run the Supabase commands in this workflow. A forked repository will not inherit these secrets from the original repository, so it will fail immediately.

Assignment

I'd like to work on this Issue myself

[github-actions[bot]]

🤖 meep morp!

Thank you for your contribution mnixo!! This Issue has been assigned to you as requested ✨

🔎 Please keep in mind that in order to give everyone a chance to contribute Issues may be unassigned if they go stale. You will be warned if the Issue is marked as stale at any point.

🔎 Please review our documentation for guidance on:

• common Patterns we follow in the code base
• conventions set for commit messages and naming functions, classes or files

💡 The core team is available for any help and will try to respond to any comments in this Issue or questions on discord as quickly as possible.

Happy coding ! 🦆