#git bot interface

History of !shallow

• A shallow clone will clone a repository to a certain "depth", which sounds like a good idea for only obtaining the latest revision of a given repo. However, they often don't work as-advertised(breaking on fetch and push operations). Instead you should consider git-archive's --remote feature, or perhaps you're really encountering a !binary problem
  By Eugene at 2014-07-24 03:06:05
• Shallow clones give you only a specified number of commit's depth. It sounds nice, but really it causes all sorts of problems if you are trying to do anything non-trivial so avoid using where-ever possible. Anybody caught doing shallow clones should be beaten viciously with their own HEAD.
  By ikke at 2013-08-28 06:53:07
• Shallow clones give you only a specified number of commit's depth. It sounds nice, but really it causes all sorts of problems if you are trying to do anything non-trivial so avoid using
  By ikke at 2013-08-28 06:52:58
• Shallow clones give you only a specified number of commit's depth. It sounds nice, but really it causes all sorts of problems if you are trying to do anything non-trivial so avoid using where-ever possible. Anybody caught doing shallow clones should be beaten viciously with their own head.
  By SethRobertson at 2012-03-28 15:51:58
• Shallow clones give you only a few commits (minimum 2) depth. However, the trade-off is that the clone is completely useless for further communications with its origin. You cannot pull further commits. You cannot push new commits. Avoid when possible
  By SethRobertson at 2012-03-28 15:45:29