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

[Docs Site] remove unnecessary DOMContentLoaded listeners #16834

Open
wants to merge 4 commits into
base: production
Choose a base branch
from

Conversation

Cherry
Copy link
Contributor

@Cherry Cherry commented Sep 14, 2024

Summary

Just some very minor optimisations by not using DOMContentLoaded events. Since all these scripts are processed by Astro, they get defer-ed as type=module, so they're guaranteed to only run when all DOM nodes are accessible.

@Cherry Cherry changed the title fix: remove unnecessary DOMContentLoaded listeners [Docs Site] remove unnecessary DOMContentLoaded listeners Sep 14, 2024
Copy link

gitguardian bot commented Sep 19, 2024

⚠️ GitGuardian has uncovered 3 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
11021221 Triggered Generic High Entropy Secret 238f8ef astro.config.mjs View secret
11021221 Triggered Generic High Entropy Secret 238f8ef astro.config.mjs View secret
11021221 Triggered Generic High Entropy Secret 238f8ef astro.config.mjs 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants