Answers: <p>The solution I found in the end is to just create a blank new project, add that to your git remotes and then push to it.</p>
  <p>You will have to manually carry over your Issues and probably some other stuff as well. Note that issues can be exported and imported as well, but they loose their comments in the process.</p>
  
Answers: CC BY-SA 4.0
Answers: 2022-12-16T18:57:32.983Z
Answers: I'm also trying to find a solution to this. The solution here is more like a last resort. I hope there is a better way than having to make a completely new repo.
Answers: andiOak
Answers: CC BY-SA 4.0
Answers: 2020-10-15T20:49:28.277Z
Answers: 2020-10-15T20:49:28.277Z
Answers: Frederik Siepe
Body: <p>I had some unwanted files in a repo which is going open-source soon. I removed the files using git-filter-branch. I noticed the project size in Gitlab growing with every such removal. Some research suggested that Gitlab has another backup layer, where the data is still in the project, which can be accessed by exporting the project.</p>
  <p>Is there a way to just reset the Gitlab storage to what the repo actually contains when being cloned?
  I'd much prefer not to do these operations again on the project file, since it is prone to data loss.</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-10-03T05:31:19.377Z
Comments: Did you check here if it is something that covers your needs? https://docs.gitlab.com/ee//////user/project/repository/reducing_the_repo_size_using_git.html#purge-files-from-gitlab-storage
Comments: akane
Tags: <gitlab>
Title: Reset Gitlab Project to Repository Content
UserDisplayName: Frederik Siepe
ThreadText: # Reset Gitlab Project to Repository Content
  
  (Asked by: username_0 on 2020-10-01)
  
  I had some unwanted files in a repo which is going open-source soon. I removed the files using git-filter-branch. I noticed the project size in Gitlab growing with every such removal. Some research suggested that Gitlab has another backup layer, where the data is still in the project, which can be accessed by exporting the project.
  
  Is there a way to just reset the Gitlab storage to what the repo actually contains when being cloned?
  I'd much prefer not to do these operations again on the project file, since it is prone to data loss.
  
  **Tags:** gitlab
  
  > **Comments:**
  > **username_1**: Did you check here if it is something that covers your needs? https://docs.gitlab.com/ee//////user/project/repository/reducing_the_repo_size_using_git.html#purge-files-from-gitlab-storage  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-10-15. Score: 1 | Accepted answer
  
  The solution I found in the end is to just create a blank new project, add that to your git remotes and then push to it.
  
  You will have to manually carry over your Issues and probably some other stuff as well. Note that issues can be exported and imported as well, but they loose their comments in the process.
  
  > **Comments:**
  > **username_2**: I'm also trying to find a solution to this. The solution here is more like a last resort. I hope there is a better way than having to make a completely new repo.  
  
  ---
  
  