Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8572349
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 11, 20262026-06-11T18:59:21+00:00 2026-06-11T18:59:21+00:00

I have git repo with two unrelated branches, master and configs. I’ve created configs,

  • 0

I have git repo with two unrelated branches, master and configs.
I’ve created configs, purged all the files and then placed in configuration files only.
Now I want to push this on remote repo, but as it were new, empty branch (without logs of all my changes and old revisions of original branch).

How can I purge all the history and push it?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-11T18:59:22+00:00Added an answer on June 11, 2026 at 6:59 pm

    Purging all the files doesn’t get rid of the history. You need to create a branch that has no history first, and the add your config files. These days git checkout has a --orphan option that makes a branch with no history. Here’s the information on the --orphan option:

    –orphan <new_branch>

    Create a new orphan branch, named <new_branch>, started from <start_point> and switch to it. The first commit made on this new branch will have no parents and it will be the root of a new history totally disconnected from all the other branches and commits.

    The index and the working tree are adjusted as if you had previously run "git checkout <start_point>". This allows you to start a new history that records a set of paths similar to <start_point> by easily running "git commit -a" to make the root commit.

    This can be useful when you want to publish the tree from a commit without exposing its full history. You might want to do this to publish an open source branch of a project whose current tree is "clean", but whose full history contains proprietary or otherwise encumbered bits of code.

    If you want to start a disconnected history that records a set of paths that is totally different from the one of <start_point>, then you should clear the index and the working tree right after creating the orphan branch by running "git rm -rf ." from the top level of the working tree. Afterwards you will be ready to prepare your new files, repopulating the working tree, by copying them from elsewhere, extracting a tarball, etc.

    Here’s a link to the documentation for checkout. You can also run git help checkout as well.

    Once you’ve created your branch without history, then when you push it to the server, it won’t have that history either. FWIW, it helps me to think of git push as "make the remote branch look the same as my local one". So if you have history, and push, it will have history. If you don’t, then the pushed branch won’t.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a git repo which has a few branches - there's the master
I have machine1 with git repo client , which has branches master and fixes_v3
Possible Duplicate: Restore a deleted file in a Git repo I have two branches
I have a git repo with two divergent branches, production and v2. I'm working
I have an entire git repo where I'd like to rename all the files
I have some symlinks in my git repo which I work on from two
I have a git repo with a dev and a master branch. Now I
I have a simple Git repo with non-branching commits in the master branch. I
I have two unrelated (not sharing any ancestor check in) Git repositories, one is
I have a repo that has two files that supposedly I changed locally. So

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.