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

Fix for eTag (#349) #350

Merged
merged 1 commit into from
Oct 31, 2024
Merged

Fix for eTag (#349) #350

merged 1 commit into from
Oct 31, 2024

Conversation

tiwa1154
Copy link
Contributor

Changes to be committed:
modified: biocompute/services.py
modified: config/settings.py

Changes to be committed:
	modified:   biocompute/services.py
	modified:   config/settings.py
@tiwa1154 tiwa1154 requested a review from HadleyKing October 31, 2024 18:15
@HadleyKing HadleyKing merged commit 8ebe1fb into main Oct 31, 2024
2 of 3 checks passed
@HadleyKing HadleyKing deleted the 24.10.31 branch October 31, 2024 18:15
Copy link

gitguardian bot commented Oct 31, 2024

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
11839907 Triggered Django Secret Key f5547a4 config/settings.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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  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.

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