You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already revoked key and generated a new one (it's in the discord)
Attempted to add the .env file to the gitignore, but it did not work because the previous team had already committed their .env files. Deleted the branch that introduced it right away, but that's not enough to fix it, so we regenerated the key as well.
We went through and made a PR that cleans up all old .env files and fixed the other mistakes in the gitignores.
Was in this commit: https://github.com/AutomatingSciencePipeline/Monorepo/blob/989eedd7ada8a44e872b7705c83d46ddeff78832/services/supabase/.env
We already revoked key and generated a new one (it's in the discord)
Attempted to add the
.env
file to the gitignore, but it did not work because the previous team had already committed their .env files. Deleted the branch that introduced it right away, but that's not enough to fix it, so we regenerated the key as well.We went through and made a PR that cleans up all old
.env
files and fixed the other mistakes in the gitignores.This guide for cleaning it up: https://cloud.google.com/docs/security/compromised-credentials
This page is where to delete keys and regenerate new ones: https://console.cloud.google.com/iam-admin/serviceaccounts?project=gladosbase&supportedpurview=project
The text was updated successfully, but these errors were encountered: