User Profile Page

[nobel10122025]

I have created a User Profile Page

[vercel[bot]]

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

Name	Status	Preview	Updated
memories-app	✅ Ready (Inspect)	Visit Preview	Aug 20, 2022 at 5:36PM (UTC)
memories-app-server	✅ Ready (Inspect)	Visit Preview	Aug 20, 2022 at 5:36PM (UTC)

[shreya024]

looks lgtm

@SMD-1 Kindly help @nobel10122025 remove the merge conflicts

[nobel10122025]

please can someone help me in resolving this merge conflict. because i have tried pulling and again pushing. but still it didnt work so provide me some suggestions

[shreya024]

please can someone help me in resolving this merge conflict. because i have tried pulling and again pushing. but still it didnt work so provide me some suggestions

Try running npm install

[nobel10122025]

i have tried that as well but it didn't work.

[nobel10122025]

I am sorry for wasting all of your time. i am giving up . please assign this to someone else. i wasnt able to resolve it . i am sorry again . and please close this PR as well. thank you for this great experience.

[soumali28]

@nobel10122025 hey dont be so sad it will solve pull the changes first in you local machine do npm install and then push it check if its working on the localhost before pushing it

[gitguardian[bot]]

⚠️ 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 | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/incidents/secrets) | MongoDB Credentials | 9773adf496379319c7533012f60e20fafcee198f | server/index.js | [View secret](https://github.com/shreya024/MemoriesApp/commit/9773adf496379319c7533012f60e20fafcee198f#diff-0861d6d6b50d7d695344bf2d86d6e5e6L18) |

🛠 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/detectors/specifics/mongo_uri#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/internal-repositories-monitoring/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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>