#jim19779
cyan lanceBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
icy lynx
Oh I mean you should never have secret keys in a file monitored by git no matter what api service you're using Stripe or otherwise
It's possible that we just added the warning recently
But you should never do that...
nova nebula
ok...I will do that....yesterday I did not have such warning....why is it bad to monitor such file by git?
icy lynx
Because those are secret keys. They aren't supposed to be shared. If they're in a file monitored by git, then they're being tracked by your version control system in its file history. This means there's risk of pushing the secret keys to Github or Bitbucket or Gitlab or whatever else you may use. And you should never do that
nova nebula
I see
icy lynx
The above warning is just to let you know that there's risk of pushing your keys to github in your current setup
nova nebula
so there is danger the key is visible to others
icy lynx
Yep
nova nebula
even if these others are team members?
icy lynx
Yes that's not safe
nova nebula
ok...got it