git clone(1) git@bitbucket.org:name/name.git -b yourBranch --single-branch --depth 10
Clone a repository into a new directory
git clone [--template=<template_directory>]
          [-l] [-s] [--no-hardlinks] [-q] [-n] [--bare] [--mirror]
          [-o <name>] [-b <name>] [-u <upload-pack>] [--reference <repository>]
          [--separate-git-dir <git dir>]
          [--depth <depth>] [--recursive|--recurse-submodules] [--] <repository>
          [<directory>]

<repository>
    The (possibly remote) repository to clone from. See the URLS section below for more information on
    specifying repositories.

<directory>
    The name of a new directory to clone into. The "humanish" part of the source repository is used if no
    directory is explicitly given (repo for /path/to/repo.git and foo for host.xz:foo/.git). Cloning into
    an existing directory is only allowed if the directory is empty.
--branch <name>, -b <name>
    Instead of pointing the newly created HEAD to the branch pointed to by the cloned repository’s HEAD,
    point to <name> branch instead. In a non-bare repository, this is the branch that will be checked
    out.
--depth <depth>
    Create a shallow clone with a history truncated to the specified number of revisions. A shallow
    repository has a number of limitations (you cannot clone or fetch from it, nor push from nor into
    it), but is adequate if you are only interested in the recent history of a large project with a long
    history, and would want to send in fixes as patches.
source manpages: git-clone