Discussions  >  CollabNet TeamForge  >  Pushing filtered-changes and cloning reduced repository

Back to topic list

Pushing filtered-changes and cloning reduced repository

Author adampreble
Full name Adam Preble
Date 2017-09-12 13:10:51 PDT
Message I had done a git filter-branch sequence to remove some binaries from my history. After filtering and removing the artifacts in the reflogs, I was able to reduce the repository locally from 125MB to 5MB. I then force pushed this to the TeamForge git repository. When I clone it, it appears the files are not in the index, but the repository is still 125MB. Does this have something to do with history protection? How do I ensure the server side of the repository is also reduced?
Attachments

« Previous message in topic | 1 of 2 | Next message in topic »

Messages

Show all messages in topic

Pushing filtered-changes and cloning reduced repository adampreble Adam Preble 2017-09-12 13:10:51 PDT
     Re: Pushing filtered-changes and cloning reduced repository markphip Mark Phippard 2017-09-12 13:51:19 PDT
Messages per page: