gitguardian[bot]
commented
2 years ago ⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🔎 Detected hardcoded secrets in your pull request
| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [336171](https://dashboard.gitguardian.com/incidents/336171?occurrence=26091200) | Generic High Entropy Secret | b79c2c1d57124cdcdb386c9e667926e602d11dbd | .github/workflows/db.yml | [View secret](https://github.com/jasperweyne/helpless-kiwi/commit/b79c2c1d57124cdcdb386c9e667926e602d11dbd#diff-2849462b60c56e2082ec2155124e370c317222081a1d7afdd0be89b72d1d83faR37) | | [336171](https://dashboard.gitguardian.com/incidents/336171?occurrence=26266219) | Generic High Entropy Secret | 12e96443de6e82ed3cd232e42764ae1624054916 | .github/workflows/db.yml | [View secret](https://github.com/jasperweyne/helpless-kiwi/commit/12e96443de6e82ed3cd232e42764ae1624054916#diff-2849462b60c56e2082ec2155124e370c317222081a1d7afdd0be89b72d1d83faL43) | | [336171](https://dashboard.gitguardian.com/incidents/336171?occurrence=26266278) | Generic High Entropy Secret | 55672d1a9240c2284861058f234c835e4d51f22a | .github/workflows/db.yml | [View secret](https://github.com/jasperweyne/helpless-kiwi/commit/55672d1a9240c2284861058f234c835e4d51f22a#diff-2849462b60c56e2082ec2155124e370c317222081a1d7afdd0be89b72d1d83faL47) | | [336171](https://dashboard.gitguardian.com/incidents/336171?occurrence=26267426) | Generic High Entropy Secret | 28eeb18563174a3d9be46eede3f9d5e93086360e | .github/workflows/db.yml | [View secret](https://github.com/jasperweyne/helpless-kiwi/commit/28eeb18563174a3d9be46eede3f9d5e93086360e#diff-2849462b60c56e2082ec2155124e370c317222081a1d7afdd0be89b72d1d83faL47) |
🛠 Guidelines to remediate hardcoded secrets
1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/internal-repositories-monitoring/integrations/git_hooks/pre_commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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!
sonarcloud[bot]
This PR adds a new github actions pipeline. The pipeline is intended to check whether the migrations are matching the entity definitions. It accomplishes this by running all migrations, after which it tries to create a new migration automatically. If this fails, that means that no changes are available, as intended. It then tries to load the fixtures used in testing, which it uses during testing of the down migration, in order to check that the down migrations function properly as well. Given the fact that an actual MySql database is necessary to execute the migrations, the choice has been made to create a new pipeline, instead of integrating it into an existing pipeline.