subhadeeproy3902 / BloxAI

Craft flowcharts and diagrams effortlessly with Blox AI. Seamlessly create visuals and rich documentation, collaborate with your team, and enjoy secure sharing. Start visualizing your ideas today!
https://blox-ai.vercel.app
MIT License
51 stars 60 forks source link

Footer section CSS style improved #330

Closed sakeel-103 closed 1 week ago

sakeel-103 commented 1 week ago

315 solved.

315 Solved.

Footer section anchor tag CSS style changed.

Description

In the footer section, the CSS of the anchor tag had a hover underline effect. In this PR, I changed it to a hover blink effect. I also added transform and transition effects to the social media section.

Type of PR

Screenshots / videos (if applicable)

Checklist:

Additional context:

[Include any additional information or context that might be helpful for reviewers.]

vercel[bot] commented 1 week ago

@sakeel-103 is attempting to deploy a commit to the subhadeep3902's projects Team on Vercel.

A member of the Team first needs to authorize it.

github-actions[bot] commented 1 week ago

Welcome to Blox AI! 🎉 Thank you for submitting your pull request. We're excited to review it! 🚀 If you haven't already, be sure to check out our site to learn more about how Blox AI makes crafting flowcharts and diagrams a breeze, and how you can get explanations from the top Google Gemini model about your creations. Start visualizing your ideas today! Visit Blox AI for more information.

gitguardian[bot] commented 1 week ago

⚠️ 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 | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/542165/incidents/secrets) | | Google API Key | 323b7373565368e54ee614fdc3a2fd3d7e47bf2d | .env.example | [View secret](https://github.com/subhadeeproy3902/BloxAI/commit/323b7373565368e54ee614fdc3a2fd3d7e47bf2d#diff-a3046da0d15a27e89f2afe639b25748a7ad4d9290af3e7b1b6c1a5533c8f0a8cL14) |
🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/googleaiza#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.

sakeel-103 commented 1 week ago

@subhadeeproy3902 here in this PR showing two checks were not successful. Please check the PR.

subhadeeproy3902 commented 1 week ago

@sakeel-103

  1. Please dont change .env.example
  2. Git pull the repo (else it gives merge conflicts)
  3. The footer animations are too childish and not at all professional. Keep them simple .. or do a basic colour change