Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The following works, repeatably, in reducing the repository down to around 2.5MB .git and 5.8MB in total. It includes the suggestions made by @jamessan above.</p> <p>This removes the objects from all branches and pushes those removals to a remote repository. That remote repository is then entirely free of these objects as far as I can tell (by the repository size dropping so dramatically.)</p> <pre><code># Configure the repository to push all existing branches &amp; tags # when none are explicitly specified git config --add remote.origin.push '+refs/tags/*:refs/tags/*' git config --add remote.origin.push '+refs/heads/*:refs/heads/*' # Make sure all local branches exist, so they get filtered for remote_branch in `git branch --all | grep -v HEAD | sed -e 's/\*//'`; do local_branch=`echo $remote_branch | sed -e 's!remotes/origin/!!'`; git checkout $local_branch; done # Prevent git &lt;1.7.7.1 from complaining about dirty working directory git update-index -q --ignore-submodules --refresh # Do the filtering across --all branches and rewrite tags # Note that this will necessarily remove signatures on tags git filter-branch -f --tree-filter "git rm -rf --ignore-unmatch modules/custom/mymigration/data/photos/*" --tag-name-filter cat -- --all # Remove the backed-up refs git for-each-ref --format="%(refname)" refs/original/ | xargs -n 1 git update-ref -d # Clear out the reflog and garbage-collect git reflog expire --expire=now --all git gc --aggressive --prune=now # Push all changes to origin - pushes tags and branches git push origin </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORemoving git repository objects entirely from all branches and tags and pushing changes to remote
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJ-P
    1. USJ-P
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORemoving git repository objects entirely from all branches and tags and pushing changes to remote
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`git push origin` doesn't push tags, by default.
      singulars
      1. PO
      1. USjamessan
    2. COIsn't that what the first line of the config settings fixes? Those two lines together change the default behaviour of optionless push-origin to push all tag and branch refs.
      singulars
      1. PO
      1. USJ-P
    3. COAh, yeah. I missed those.
      singulars
      1. PO
      1. USjamessan
 

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