Skip to content
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

feat:获取任意省或者市的中国石化92号汽油最新指导价格 #49

Closed
wants to merge 133 commits into from

Conversation

Ashesttt
Copy link
Collaborator

@Ashesttt Ashesttt commented Feb 4, 2024

No description provided.

# Conflicts:
#	config.ini.example
#	wechatter/app/app.py
#	wechatter/config/parsers/__init__.py
Copy link

gitguardian bot commented Feb 4, 2024

⚠️ GitGuardian has uncovered 9 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 GitGuardian status Secret Commit Filename
9452179 Triggered Generic High Entropy Secret 3933d87 wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret a72e73f wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret bc61160 wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret b84e710 wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret bc61160 wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret 9ed82db wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret 6f135a8 wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret 3933d87 wechatter/commands/_commands/food_calories.py View secret
9452179 Triggered Generic High Entropy Secret 9ed82db wechatter/commands/_commands/food_calories.py View secret
🛠 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 the best practices.
  3. Revoke and rotate these secrets.
  4. 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


🦉 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!

@Cassius0924 Cassius0924 closed this Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants