Local repository cache about gitness HOT 4 CLOSED

@knoopx travis works around that by just cloning a depth of 50?

https://travis-ci.org/rails/rails/jobs/18690738

$ git clone --depth=50 --branch=master git://github.com/rails/rails.git rails/rails

remote: Counting objects: 19660, done.
remote: Compressing objects: 100% (10381/10381), done.
remote: Total 19660 (delta 12408), reused 14804 (delta 8669)
Receiving objects: 100% (19660/19660), 8.87 MiB | 118.00 KiB/s, done.
Resolving deltas: 100% (12408/12408), done.

Versus:

remote: Counting objects: 406499, done.
remote: Compressing objects: 100% (110094/110094), done.
Receiving objects:  62% (252585/406499), 33.39 MiB | 117.00 KiB/s
...

from gitness.

@luislavena good suggestion. adding --depth is really simple. let's try this first

from gitness.

I checked the travis's process.

It sets --depth=50 by default. When we specified the git clone depth on .travis.yml as described below, travis sets its value as the depth.

git:
  depth: 1

Travis's manner looks good for me because developers can specify the git clone depth as they like.

I will try to implement this function later.

from gitness.

@bradrydzewski I think this can be closed due the work done in #62?

from gitness.