Push Existing Files

[legend-ron2025]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

How do i push my existing files to my repositories??
and replace it with the old one?

[zenformality]

1.Clone the repository to a new folder on your computer.
2.Delete everything inside that folder except for the hidden .git directory.
3.Copy your new files into that same folder.
4.Stage, commit, and push as normal (git add . , git commit , git push ).

[AbhinavPabbaraju]

You can push your existing local files to a GitHub repository and replace its contents, but the exact steps depend on whether you want to overwrite history or just update files.

---

Case 1: Push local files and overwrite remote (most common)

If you already have files on your computer:

# Go to your project folder
cd your-project

# Initialize git (if not already)
git init

# Add remote repository
git remote add origin https://github.com/your-username/your-repo.git

# Add all files
git add .

# Commit
git commit -m "Initial commit"

# Force push (overwrites remote content)
git push -f origin main

NOTE: This will replace everything on the remote repository.

---

Case 2: Replace old repo with new content (clean reset)

If the repo already has content and you want to completely replace it:

git init
git add .
git commit -m "Replace old content"

git branch -M main
git remote add origin https://github.com/your-username/your-repo.git

git push --force origin main

---

Important Notes

• --force will overwrite history on GitHub
• This can affect collaborators (they may need to re-clone)
• Use only if you're sure you want to replace everything

---

[snackoverflowasad]

You just need to add, commit, and push. In your project folder:
bashgit add .
git commit -m "update files"
git push origin main
That's it. Git will overwrite the old files in your repo with whatever you have locally.
A few things that might trip you up:
If your branch is called master instead of main, swap that in the push command. If you get a rejection saying the remote has changes you don't have locally, run git pull origin main first, then push again.
If you haven't connected your local folder to a repo yet, you'll need this first:
bashgit remote add origin https://github.com/your-username/your-repo.git
Then do the add/commit/push steps above.
Does that cover your situation, or are you running into a specific error message?

[Gecko51]

If you're already connected to a remote repo, it's just:

git add .
git commit -m "update files"
git push origin main

To completely replace everything on the remote (overwrites history):

git push --force origin main

Starting from scratch with no git setup yet:

git init
git add .
git commit -m "initial commit"
git remote add origin https://github.com/yourname/yourrepo.git
git push -u origin main

If push gets rejected with "non-fast-forward," run git pull origin main --rebase first, then push again. That happens when the remote has commits your local copy doesn't know about. If you don't care about those remote commits and want to overwrite anyway, --force skips the pull.

[shuvo-sir]

Hi! If you want to push your local files to an existing GitHub repository and "replace" what is currently there with your local version, you can follow these steps.

1. Initialize and Commit your Local Files
   Open your terminal in the folder where your files are located:

Bash
git init
git add .
git commit -m "Replacing old files with current local version"
2. Link to your GitHub Repository
Copy the URL of your repository from GitHub and run:

Bash
git remote add origin https://github.com/YOUR_USERNAME/YOUR_REPO_NAME.git
(If it says "remote origin already exists," run git remote set-url origin instead.)

3. Force Push to Overwrite (The "Replace" Step)
   Since you want to replace the old files with the new ones, you need to use a "force push." This tells GitHub to ignore the history of the old files and use yours instead.

Bash
git push -u origin main --force
(Note: If your main branch is called master, use master instead of main.)