Skip to content

testing dagger#5

Open
OnlyLight wants to merge 1 commit into
mainfrom
feat/demo-2
Open

testing dagger#5
OnlyLight wants to merge 1 commit into
mainfrom
feat/demo-2

Conversation

@OnlyLight
Copy link
Copy Markdown
Owner

testing dagger check unittest

Comment thread website/src/App.js Outdated
<CssBaseline />
<Container maxWidth='lg'>
<Header title='Crawler System Testing 1' sections={sections} />
<Header title='Crawler System Testing 2' sections={sections} />
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<Header title='Crawler System Testing 2' sections={sections} />
<Header title='Crawler System Testing 1' sections={sections} />

@OnlyLight OnlyLight force-pushed the feat/demo-2 branch 2 times, most recently from 27cfe47 to 168818c Compare June 12, 2025 07:07
@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented Jun 12, 2025

⚠️ 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
17810643 Triggered Generic Password 7a7ba34 my.secrets 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