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 dexie performance #291

Merged
merged 42 commits into from
Jun 11, 2024
Merged

Feature dexie performance #291

merged 42 commits into from
Jun 11, 2024

Conversation

Ratatinator97
Copy link
Contributor

No description provided.

Copy link

netlify bot commented Jun 10, 2024

Deploy Preview for cranky-mestorf-b134b5 ready!

Name Link
🔨 Latest commit c4242f5
🔍 Latest deploy log https://app.netlify.com/sites/cranky-mestorf-b134b5/deploys/66680b73390cae0008b5787a
😎 Deploy Preview https://deploy-preview-291--cranky-mestorf-b134b5.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 68 (🔴 down 6 from production)
Accessibility: 97 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: 100 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

gitguardian bot commented Jun 10, 2024

⚠️ 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 GitGuardian status Secret Commit Filename
7814939 Triggered Company Email Password 4d3aeb2 lang/sk.json View secret
4506499 Triggered Company Email Password 4d3aeb2 lang/en.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.

@Ratatinator97 Ratatinator97 merged commit 77f5fcf into stable Jun 11, 2024
4 of 7 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.

1 participant