summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCiro Santilli <ciro.santilli@gmail.com>2014-10-03 12:21:23 +0200
committerCiro Santilli <ciro.santilli@gmail.com>2014-10-03 12:21:23 +0200
commit6014e28c2df977643ed4d1c5480158db0e9a09eb (patch)
tree10bc8d0cd94e44cf6c5023bdaecc11297642aca5
parenta3d90c5045ae322a013484165cdebcd764dc5d69 (diff)
downloadgitlab-ce-6014e28c2df977643ed4d1c5480158db0e9a09eb.tar.gz
Remove outdated comment on the project test seed
-rw-r--r--spec/factories/projects.rb10
1 files changed, 0 insertions, 10 deletions
diff --git a/spec/factories/projects.rb b/spec/factories/projects.rb
index 5324654c48c..23314b3b1a4 100644
--- a/spec/factories/projects.rb
+++ b/spec/factories/projects.rb
@@ -47,16 +47,6 @@ FactoryGirl.define do
end
end
- # Generates a test repository from the repository stored under `spec/seed_project.tar.gz`.
- # Once you run `rake gitlab:setup`, you can see what the repository looks like under `tmp/repositories/gitlabhq`.
- # In order to modify files in the repository, you must untar the seed, modify and remake the tar.
- # Before recompressing, do not forget to `git checkout master`.
- # After recompressing, you need to run `RAILS_ENV=test bundle exec rake gitlab:setup` to regenerate the seeds under tmp.
- #
- # If you want to modify the repository only for an specific type of tests, e.g., markdown tests,
- # consider using a feature branch to reduce the chances of collision with other tests.
- # Create a new commit, and use the same commit message that you will use for the change in the main repo.
- # Changing the commig message and SHA of branch `master` may break tests.
factory :project, parent: :empty_project do
path { 'gitlabhq' }