-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[chore] Change check milestone rules #342
Conversation
Signed-off-by: Kirill Kramorov <[email protected]>
{ | ||
"credentional": { | ||
"user": "testuser", | ||
"password": "deese0wie2tahph2mooyaiPoorie0Nah" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛑 Gitleaks has detected a secret with rule-id generic-api-key
in commit 42e7604.
If this secret is a true positive, please rotate the secret ASAP.
If this secret is a false positive, you can add the fingerprint below to your .gitleaksignore
file and commit the change to this branch.
echo 42e7604e95099783626dca9c46edb27436db70f7:1.json:generic-api-key:4 >> .gitleaksignore
#!/usr/bin/env bash | ||
|
||
url="https://api.github.com" | ||
token="ghp_CTbv1bPL14y0TtwfPveRYS3Cred4oken" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛑 Gitleaks has detected a secret with rule-id generic-api-key
in commit 42e7604.
If this secret is a true positive, please rotate the secret ASAP.
If this secret is a false positive, you can add the fingerprint below to your .gitleaksignore
file and commit the change to this branch.
echo 42e7604e95099783626dca9c46edb27436db70f7:1.sh:generic-api-key:4 >> .gitleaksignore
@@ -0,0 +1,8 @@ | |||
# Тестовый ключ для проверки gitleaks | |||
-----BEGIN OPENSSH PRIVATE KEY----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛑 Gitleaks has detected a secret with rule-id private-key
in commit 42e7604.
If this secret is a true positive, please rotate the secret ASAP.
If this secret is a false positive, you can add the fingerprint below to your .gitleaksignore
file and commit the change to this branch.
echo 42e7604e95099783626dca9c46edb27436db70f7:id-rsa:private-key:2 >> .gitleaksignore
Signed-off-by: Kirill Kramorov <[email protected]>
@@ -0,0 +1,8 @@ | |||
# Тестовый ключ для проверки gitleaks | |||
-----BEGIN OPENSSH PRIVATE KEY----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛑 Gitleaks has detected a secret with rule-id private-key
in commit cfcea86.
If this secret is a true positive, please rotate the secret ASAP.
If this secret is a false positive, you can add the fingerprint below to your .gitleaksignore
file and commit the change to this branch.
echo cfcea869fb6a3a987edb7932f3e4489aecafaa74:id-rsa2:private-key:2 >> .gitleaksignore
2b89007
to
7eb3534
Compare
Description
Why do we need it, and what problem does it solve?
Why do we need it in the patch release (if we do)?
What is the expected result?
Checklist
Changelog entries