Core testing fixes #831
Core testing fixes #831
Conversation
update coverage-package and config LGTM
* updated user tests, removed facility tests Co-authored-by: Aakash Singh <46787056+sainAk@users.noreply.github.com>
Added tests workflow
Merge master to testing
optimized tests workflow
* removed old tests * work in progress * Trying after removing report * Trying to add step of coverage report * Update setup.cfg * Update setup.cfg * Update setup.cfg * final update to test workflow * fixed mistake and testing pip caches * it should solve * updated cache settings and updated coveragerc
fix test warnings and parallel runs
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 196640 | Generic Private Key | 00d57de | config/settings/base.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating 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 git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
2 similar comments
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 196640 | Generic Private Key | 00d57de | config/settings/base.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating 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 git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 196640 | Generic Private Key | 00d57de | config/settings/base.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating 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 git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
|
Approving without testing. |
In this PR
#794