Conversation
Routing and some of templates and packages are included
|
| Secret | Commit | Filename | Detected At | |
|---|---|---|---|---|
| Django Secret Key | 61205d8 | Informatsy/Informatsy/settings.py | 10:31 May 27th, 2021 | View secret |
| Django Secret Key | 1922059 | informatsy/informatsy/settings.py | 23:41 May 29th, 2021 | View secret |
🛠 How to resolve this
-
Understand the implications of revoking this secret by examining where it is used in your code.
-
Replace and store your secret safely. Learn here the best practices
-
Revoke and rotate this secret
-
If possible, rewrite your git history to remove all evidence of the secret leak. Please beware this is not a trivial operation. You might completely break other contributing developers’ workflow and you risk accidentally deleting work in progress.
💡 To avoid such incidents in the future, consider following these best practices for managing and storing secrets including API keys and other credentials.
You are seeing this because you or someone else has authorized GitGuardian to scan pull requests
No description provided.