Skip to content

Feat: Localization#159

Draft
Kyle-L wants to merge 6 commits intomainfrom
feat/localization
Draft

Feat: Localization#159
Kyle-L wants to merge 6 commits intomainfrom
feat/localization

Conversation

@Kyle-L
Copy link
Copy Markdown
Member

@Kyle-L Kyle-L commented Sep 22, 2025

Description 📝

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

How Has This Been Tested? 🔍

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

  • Test A
  • Test B

Motivation and Context 🎯

Please describe the reason for the changes.

ClickUp Task 📌

CU-XXXX

@Kyle-L Kyle-L self-assigned this Sep 22, 2025
@Kyle-L Kyle-L added the work-in-progress The code changes are still being developed label Sep 22, 2025
@gitguardian
Copy link
Copy Markdown

gitguardian bot commented Sep 22, 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
21103024 Triggered Generic Password 6462b64 pnpm-lock.yaml 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

work-in-progress The code changes are still being developed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant