Update CONTRIBUTING.md

[hrishav398]

Added keeping your local copy updated part

Pull Request

Description

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Style update (formatting, renaming)
• ♻️ Code refactor (no functional changes)
• ⚡️ Performance improvement
• ✅ Test update
• 🔨 Build configuration update
• 🔒 Security update

Changes Made

Added the following:
Keeping Your Local Copy Up to Date
After your feature has been accepted and merged, it's important to ensure your local copy is up to date before starting any new work. Especially if you're about to begin work on a different feature, follow these steps:

git checkout main             # Switch back to the main branch
git pull                      # Update your local copy with the latest changes
git checkout -b new_branch_name  # Create a new branch for your next feature

This ensures you're always working on the latest version of the codebase.

Screenshots

Testing

1. Steps to reproduce:
2. Test environment:
   • OS:
   • Node version:
   • Browser (if applicable):

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

Dependencies

Database Changes

• No database changes
• Database changes included (describe below):

API Changes

• No API changes
• API changes included (describe below):

Performance Impact

• No performance impact
• Performance impact (describe below):

Security Considerations

• No security implications
• Security implications considered (describe below):

Additional Notes

Reviewer Notes

Post-Deployment Steps

• No post-deployment steps needed
• Post-deployment steps required (describe below):

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.