Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>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 <code>git checkout</code> has a <code>--orphan</code> option that makes a branch with no history. Here's the information on the <code>--orphan</code> option:</p> <blockquote> <p>--orphan &lt;new_branch></p> <p>Create a new orphan branch, named &lt;new_branch>, started from &lt;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.</p> <p>The index and the working tree are adjusted as if you had previously run "git checkout &lt;start_point>". This allows you to start a new history that records a set of paths similar to &lt;start_point> by easily running "git commit -a" to make the root commit.</p> <p>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.</p> <p>If you want to start a disconnected history that records a set of paths that is totally different from the one of &lt;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.</p> </blockquote> <p>Here's a link to the documentation for <a href="http://git-scm.com/docs/git-checkout" rel="noreferrer">checkout</a>. You can also run <code>git help checkout</code> as well.</p> <p>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 <code>git push</code> 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.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to push new branch without history
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDMI
    1. USJohn Szakmeister
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to push new branch without history
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload