Home / Questions / 55274
Accepted
toledano
Asked: 2020-03-15 10:16:52 +0800 CST 2020-03-15 10:16:52 +0800 CST

Create a fileless branch of an existing .git repository

  • 772

I want to create a fileless branch for an existing repository .

What I have done is this:

  • make a new branch
  • delete everything (except .gitand .gitignore, that is, the files of my project, not the control files or those generated by the editors)
  • dogit add .
  • and then docommit

But it looks like a brute force solution to me.

Ask

How do I create a fileless branch of an existing project?

Bonus: My repository is on , is there a specific way to achieve this for this specific platform? If there is, what is it?

git

2 Answers

  1. Best Answer

    There is an option called orphanfor the command git checkout to do what I think you need which is:

    Create a fileless branch of an existing repository

    Your description in English

    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.

    Translation (staff (if you have a better one feel free to edit my answer) )

    Creates an orphan branch, called <nueva_rama>, started from <punto_de_inicio>and changes it to this. The first commitfact in this new branch will have no parents and will be the root of a new history totally disconnected from all other branches andcommits

    For which in conclusion you could do the following:

    // Aquí creamos nuestra rama sin padre, independiente y sin historia
// pero con los archivos 'track' y 'untrack' que tengamos
// actualmente en nuestro directorio 
git checkout --orphan nueva_rama_independiente_de_todas_las_otras

    (The above is thanks to the clarification of user sstan )

    // Como los archivos seguirán presentes después de crear la rama
// procedemos a eliminar todos los archivos que han sido y/o estado
// 'track' y 'untrack'
git rm --cached -rf .

    (The above is thanks to the advice (very useful and true by the way) of the user Jhd )

    Note that it is not necessary to use the option -bsince using --orphanit will move from the current branch to the created one, as can be read in the description of this option.

    • 3

  2. just make another branch apart from the master and develop with nothing so that what you have in production and development does not affect you. and from that same branch that you make you delete everything and commit

    so you barely leave the important branches intact

    • 0