[Bug] Not able to sign up #112

[AE-Hertz]

[Bug] Not able to sign up #112

Closes: #112

Implemented following things:

• social login signin & signup with google
• social login singin & signup with twitter
• social login signin & signup with github
• social login pops up if their is any interruption with signin
• used firebase and
• firebase dep shipped
• .gitignore shipped
• .env.example for firebase keys shipped.

Workings:

Provider Google

Screen.Recording.2024-11-10.134831.mp4

Provider X

Untitled.video.-.Made.with.Clipchamp.mp4

Provider Github

Screen.Recording.2024-11-10.134926.mp4

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pen-craft	❌ Failed (Inspect)			Nov 10, 2024 8:27am

[AE-Hertz]

@AkshitLakhera can you review this PR. and also upgrade level to level3 that would be appreciated. thank you.

[gitguardian]

⚠️ 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.

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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9682237	Triggered	Base64 Generic High Entropy Secret	8dd2ef8	backend/wrangler.toml	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

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}