what's the best way to deal with bigquery credentials in a public repo? i'm working through the instructions and it says input your creds and evidence will 'save them locally' which makes me think it would potentially commit them?

@rapid-grass-65397 👋 the .evidence directory is gitignored in the template project

oh sweetttt

In prod it’s environment variables, but we should probably move to that across both.

my bad, i shoulda noticed that, i saw

.evidence

getting added but missed that

.evidence/template

where setting are was ignored, awesome, so sort of dumb question as i get my head around this, that's ignored, i commit, somebody opens it locally or in a codespace and runs

npm run dev

-- does it then generate that folder again?

Yes exactly

sweeet okay ty! that makes sense

But I just listened to your note and see where you’re headed. You can def set up a codespace with environment variables that someone could swap into a .env file, or similar

cool cool that was about to be my next q, awesome 🙏 will keep heading down that road then ty!

@bright-smartphone-11251 has done a bunch w/ codespaces, so we can def help you get that set up (and we’ll document it)