🚀 How to Switch Your Local LibreChat Repo to Your Forked Version

You don’t need to delete your current local repository or do a fresh git init. You can easily associate (or switch) your existing local repo to your forked GitHub repository without losing any local changes or history. 🌟

Step 1: Make Sure You’ve Forked the Repo on GitHub 🍴

• Go to https://github.com/danny-avila/LibreChat
• Click Fork → create your own copy (e.g., https://github.com/YOUR-USERNAME/LibreChat)

Step 2: In Your Local Repo, Change the Remote Origin 🔄

Open PowerShell or your terminal in your local LibreChat folder and run these commands:

# Check current remote (it probably points to the original danny-avila repo)
git remote -v

# You’ll likely see something like:
origin  https://github.com/danny-avila/LibreChat.git (fetch)
origin  https://github.com/danny-avila/LibreChat.git (push)

# Now switch it to your fork:

# Remove the old origin (optional but clean)
git remote remove origin

# Add your fork as the new origin
git remote add origin https://github.com/YOUR-USERNAME/LibreChat.git
  

Replace YOUR-USERNAME with your actual GitHub username. ✅

Step 3: Verify and Push 🔍

git remote -v
  

Now it should show your fork for both fetch and push.

If you have any local commits you want to keep:

git push -u origin main
  

(The -u sets up tracking so future git push/git pull work without specifying the branch.)

Optional: Keep the Original Repo as "Upstream" for Updates 🆙

To easily pull future updates from the official LibreChat repo:

git remote add upstream https://github.com/danny-avila/LibreChat.git
  

Then in the future:

git fetch upstream
git merge upstream/main
# or git rebase upstream/main if you prefer rebasing

git push origin main
  

🎉 Summary

• No need to delete anything or start over. 🛡️
• Just change the remote URL to point to your fork.
• Optionally add upstream to stay in sync with the original project.

Once this is done, connect this repo to Railway and every git push will trigger a deploy with your changes! 🚀✨