Make SUPABASE_ACCESS_TOKEN non-personal and instead project specific #393
Description
The Supabase CLI requires a few environment variables to run in non-interactive mode.
SUPABASE_ACCESS_TOKENis your personal access token
Forcing us to use the personal access token that has access to the whole account seems like a security issue. I would like to generate a project specific access token that I can use in the respective GitHub actions repository.
If someone gets access to my personal access token in one GitHub repository, then that access token can be used on all my Supabase organization and all my projects.