#Api Key config
1 messages · Page 1 of 1 (latest)
<@&1004656351647117403> please have a look, thanks.
Yes, don't push secrets.
don't publish secrets in repositories
There's a reason you get the warning.
Read it from a file you don't push, a key vault, ... But don't push it!
Why would you want to hardcode your API key in the first place? GitHub is doing you a favor by not accepting it.
In fact, there are scrapers running pretty much 24/7, looking for people stupid enough to publish their API keys. These scrapers will look at every git commit and check for these keys, so as soon as you pushed it, your API key is effectively stolen.
easiest way is from an env