Adding a proper Readme to the repo.

[HemantMedhsia]

This pull request improves the README.md file for the Rupee: Expense Tracker App. The changes aim to provide better readability, structure, and completeness for new developers and contributors.

✅ What's Improved:

• Clear and polished project introduction to explain the purpose of the app
• Structured Table of Contents for quick navigation
• Step-by-step Installation Guide for both backend and frontend with code blocks
• Authentication and API Documentation added for Expenses, Incomes, and Savings
• Commit message guidelines for contributors
• Contribution section to guide community involvement
• License and credits at the end

📌 Why These Changes?

• Makes the project beginner-friendly and professional
• Helps contributors understand project setup and API structure quickly
• Improves SEO and visibility on GitHub

Encourages open-source collaboration

[vercel]

@HemantMedhsia is attempting to deploy a commit to the narang24's projects Team on Vercel.

A member of the Team first needs to authorize it.

[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
-	-	MongoDB Credentials	2906deb	backend/.env	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.}