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

Feature responsive #147

Merged
merged 14 commits into from
Oct 22, 2023
Merged

Feature responsive #147

merged 14 commits into from
Oct 22, 2023

Conversation

francoissmith
Copy link
Collaborator

No description provided.

@codecov
Copy link

codecov bot commented Oct 22, 2023

Codecov Report

Merging #147 (0c6d61a) into development (c804c41) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development     #147   +/-   ##
============================================
  Coverage        84.26%   84.26%           
============================================
  Files               24       24           
  Lines             1239     1239           
  Branches           117      117           
============================================
  Hits              1044     1044           
  Misses             191      191           
  Partials             4        4           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@gitguardian
Copy link

gitguardian bot commented Oct 22, 2023

⚠️ GitGuardian has uncovered 2 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
8491494 Generic High Entropy Secret 0c6d61a src/Blue-Skies.postman_collection.json View secret
8491494 Generic High Entropy Secret 0c6d61a src/Blue-Skies.postman_collection.json 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!

@francoissmith francoissmith merged commit 38de058 into development Oct 22, 2023
5 checks passed
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