summaryrefslogtreecommitdiff
path: root/spec/services/projects/fork_service_spec.rb
diff options
context:
space:
mode:
authorToon Claes <toon@gitlab.com>2018-08-02 13:30:24 +0200
committerToon Claes <toon@gitlab.com>2018-08-20 16:39:32 +0200
commitf4f321b9023d5aba76541f442fe1061d70186f27 (patch)
tree3ad1567bde2e55c9e3b6a0ff0dba1520c890a36b /spec/services/projects/fork_service_spec.rb
parent7c9983c721ab47d25c9d437035e04b385e8af7c9 (diff)
downloadgitlab-ce-f4f321b9023d5aba76541f442fe1061d70186f27.tar.gz
Clean up LFS objects when creating fork relation
A forked project stores its LFS objects in the `forked_from_project`. So the LFS objects become inaccessible, and therefore delete them from the database so they'll get cleaned up. To be refactored when implementing https://gitlab.com/gitlab-org/gitlab-ce/issues/39769
Diffstat (limited to 'spec/services/projects/fork_service_spec.rb')
-rw-r--r--spec/services/projects/fork_service_spec.rb8
1 files changed, 8 insertions, 0 deletions
diff --git a/spec/services/projects/fork_service_spec.rb b/spec/services/projects/fork_service_spec.rb
index f89f9b54f53..947cb61038d 100644
--- a/spec/services/projects/fork_service_spec.rb
+++ b/spec/services/projects/fork_service_spec.rb
@@ -264,6 +264,14 @@ describe Projects::ForkService do
expect(fork_from_project.forks_count).to eq(1)
end
+
+ it 'leaves no LFS objects dangling' do
+ create(:lfs_objects_project, project: fork_to_project)
+
+ expect { subject.execute(fork_to_project) }
+ .to change { fork_to_project.lfs_objects_projects.count }
+ .to(0)
+ end
end
end
end