Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You might want to try pushing an empty local repo with the <a href="https://www.kernel.org/pub/software/scm/git/docs/git-push.html"><code>--mirror</code> flag</a> (emphasis mine):</p> <blockquote> <pre><code>--mirror </code></pre> <p>Instead of naming each ref to push, specifies that all refs under refs/ (which includes but is not limited to <code>refs/heads/</code>, <code>refs/remotes/</code>, and <code>refs/tags/</code>) be mirrored to the remote repository. Newly created local refs will be pushed to the remote end, locally updated refs will be force updated on the remote end, and <strong><em>deleted refs will be removed from the remote end</em></strong>. This is the default if the configuration option <code>remote.&lt;remote&gt;.mirror</code> is set.</p> </blockquote> <p>If your repo is on GitHub, you'll get this error if <code>master</code> is set to the default branch when trying to push:</p> <pre><code>$ mkdir practice; cd practice; $ git init; git remote add origin git@github.com:user/practice.git; $ git push origin --mirror remote: error: refusing to delete the current branch: refs/heads/master To git@github.com:user/practice.git ! [remote rejected] master (deletion of the current branch prohibited) error: failed to push some refs to 'git@github.com:user/practice.git' </code></pre> <p>I got around this by making an initial commit, then pushing.</p> <p><strong>Obligatory Warning</strong>: this will, of course, completely wipe out all of your history and commits in your remote repo&mdash;all references, all branches, all tags, etc. Make sure this is actually what you want to do. Of course, you can always make a backup clone of your remote repo before doing this, in case you want to keep it around for whatever reason.</p> <p>Also note that none of the commits will actually be deleted right away. They'll just become <em>dangling</em> commits, meaning that they're not reachable from a branch. Eventually they'll get garbage collected by Git repos, but if you have access to your remote repo, you can manually start the garbage collection with <code>git gc</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. PODelete or remove all history, commits, and branches from a remote Git repo?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODelete or remove all history, commits, and branches from a remote Git repo?
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAwesome... that did the trick, and has the elegant simplicity of the right solution! (I also had to add a simple commit). Thanks!
      singulars
      1. PO
      1. USStabledog
    2. COA follow-up on this from (http://stackoverflow.com/a/18116141/237059). I experimented locally and discovered that pushing with --mirror doesn't actually shrink the origin repo: the disk usage is the same, but the history is no longer accessible, and when that repo is re-cloned, the clone is tiny. So the effect produces what I need for practical matters... I don't really care that an otherwise-inaccessible origin is consuming more disk space than it should. But that's a surprising outcome nevertheless.
      singulars
      1. PO
      1. USStabledog
    3. CO@Stabledog whoever manages the remote repo (your repo hosting provider, for example), will more than likely run `git gc` (garbage collect) eventually, which will remove all the dangling commits (commits that aren't reachable from a branch/reference), so the disk usage on the remote will eventually shrink to something like what you have with your local clone. This is something I mentioned in [this comment](http://stackoverflow.com/questions/18112966/how-to-delete-purge-remove-all-history-commits-references-branches-from-a-remote/18113182?noredirect=1#comment26519830_18112966).
      singulars
      1. PO
      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