Git push 命令

更新时间: 2019-07-13 17:17

git-push - Update remote refs along with associated objects

语法

git push [--all | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
    [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-v | --verbose]
    [-u | --set-upstream] [--push-option=<string>]
    [--[no-]signed|--signed=(true|false|if-asked)]
    [--force-with-lease[=<refname>[:<expect>]]]
    [--no-verify] [<repository> [<refspec>...]]

参数

<repository>
    The "remote" repository that is destination of a push operation. This parameter can be either a URL (see the section GIT URLS
    below) or the name of a remote (see the section REMOTES below).

<refspec>...
    Specify what destination ref to update with what source object. The format of a <refspec> parameter is an optional plus +, followed
    by the source object <src>, followed by a colon :, followed by the destination ref <dst>.

    The <src> is often the name of the branch you would want to push, but it can be any arbitrary "SHA-1 expression", such as master~4
    or HEAD (see gitrevisions(7)).

    The <dst> tells which ref on the remote side is updated with this push. Arbitrary expressions cannot be used here, an actual ref
    must be named. If git push [<repository>] without any <refspec> argument is set to update some ref at the destination with <src>
    with remote.<repository>.push configuration variable, :<dst> part can be omitted--such a push will update a ref that <src> normally
    updates without any <refspec> on the command line. Otherwise, missing :<dst> means to update the same ref as the <src>.

    The object referenced by <src> is used to update the <dst> reference on the remote side. By default this is only allowed if <dst>
    is not a tag (annotated or lightweight), and then only if it can fast-forward <dst>. By having the optional leading +, you can tell
    Git to update the <dst> ref even if it is not allowed by default (e.g., it is not a fast-forward.) This does not attempt to merge
    <src> into <dst>. See EXAMPLES below for details.

    tag <tag> means the same as refs/tags/<tag>:refs/tags/<tag>.

    Pushing an empty <src> allows you to delete the <dst> ref from the remote repository.

    The special refspec : (or +: to allow non-fast-forward updates) directs Git to push "matching" branches: for every branch that
    exists on the local side, the remote side is updated if a branch of the same name already exists on the remote side.

--all
    Push all branches (i.e. refs under refs/heads/); cannot be used with other <refspec>.

--prune
    Remove remote branches that don't have a local counterpart. For example a remote branch tmp will be removed if a local branch with
    the same name doesn't exist any more. This also respects refspecs, e.g.  git push --prune remote refs/heads/*:refs/tmp/* would make
    sure that remote refs/tmp/foo will be removed if refs/heads/foo doesn't exist.

--mirror
    Instead of naming each ref to push, specifies that all refs under refs/ (which includes but is not limited to refs/heads/,
    refs/remotes/, and refs/tags/) be mirrored to the remote repository. Newly created local refs will be pushed to the remote end,
    locally updated refs will be force updated on the remote end, and deleted refs will be removed from the remote end. This is the
    default if the configuration option remote.<remote>.mirror is set.

-n, --dry-run
    Do everything except actually send the updates.

--porcelain
    Produce machine-readable output. The output status line for each ref will be tab-separated and sent to stdout instead of stderr.
    The full symbolic names of the refs will be given.

--delete
    All listed refs are deleted from the remote repository. This is the same as prefixing all refs with a colon.

--tags
    All refs under refs/tags are pushed, in addition to refspecs explicitly listed on the command line.

--follow-tags
    Push all the refs that would be pushed without this option, and also push annotated tags in refs/tags that are missing from the
    remote but are pointing at commit-ish that are reachable from the refs being pushed. This can also be specified with configuration
    variable push.followTags. For more information, see push.followTags in git-config(1).

--[no-]signed, --signed=(true|false|if-asked)
    GPG-sign the push request to update refs on the receiving side, to allow it to be checked by the hooks and/or be logged. If false
    or --no-signed, no signing will be attempted. If true or --signed, the push will fail if the server does not support signed pushes.
    If set to if-asked, sign if and only if the server supports signed pushes. The push will also fail if the actual call to gpg --sign
    fails. See git-receive-pack(1) for the details on the receiving end.

--[no-]atomic
    Use an atomic transaction on the remote side if available. Either all refs are updated, or on error, no refs are updated. If the
    server does not support atomic pushes the push will fail.

-o, --push-option
    Transmit the given string to the server, which passes them to the pre-receive as well as the post-receive hook. The given string
    must not contain a NUL or LF character.

--receive-pack=<git-receive-pack>, --exec=<git-receive-pack>
    Path to the git-receive-pack program on the remote end. Sometimes useful when pushing to a remote repository over ssh, and you do
    not have the program in a directory on the default $PATH.

--[no-]force-with-lease, --force-with-lease=<refname>, --force-with-lease=<refname>:<expect>
    Usually, "git push" refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it.

    This option overrides this restriction if the current value of the remote ref is the expected value. "git push" fails otherwise.

    Imagine that you have to rebase what you have already published. You will have to bypass the "must fast-forward" rule in order to
    replace the history you originally published with the rebased history. If somebody else built on top of your original history while
    you are rebasing, the tip of the branch at the remote may advance with her commit, and blindly pushing with --force will lose her
    work.

    This option allows you to say that you expect the history you are updating is what you rebased and want to replace. If the remote
    ref still points at the commit you specified, you can be sure that no other people did anything to the ref. It is like taking a
    "lease" on the ref without explicitly locking it, and the remote ref is updated only if the "lease" is still valid.

    --force-with-lease alone, without specifying the details, will protect all remote refs that are going to be updated by requiring
    their current value to be the same as the remote-tracking branch we have for them.

    --force-with-lease=<refname>, without specifying the expected value, will protect the named ref (alone), if it is going to be
    updated, by requiring its current value to be the same as the remote-tracking branch we have for it.

    --force-with-lease=<refname>:<expect> will protect the named ref (alone), if it is going to be updated, by requiring its current
    value to be the same as the specified value <expect> (which is allowed to be different from the remote-tracking branch we have for
    the refname, or we do not even have to have such a remote-tracking branch when this form is used). If <expect> is the empty string,
    then the named ref must not already exist.

    Note that all forms other than --force-with-lease=<refname>:<expect> that specifies the expected current value of the ref
    explicitly are still experimental and their semantics may change as we gain experience with this feature.

    "--no-force-with-lease" will cancel all the previous --force-with-lease on the command line.

    A general note on safety: supplying this option without an expected value, i.e. as --force-with-lease or
    --force-with-lease=<refname> interacts very badly with anything that implicitly runs git fetch on the remote to be pushed to in the
    background, e.g.  git fetch origin on your repository in a cronjob.

    The protection it offers over --force is ensuring that subsequent changes your work wasn't based on aren't clobbered, but this is
    trivially defeated if some background process is updating refs in the background. We don't have anything except the remote tracking
    info to go by as a heuristic for refs you're expected to have seen & are willing to clobber.

    If your editor or some other system is running git fetch in the background for you a way to mitigate this is to simply set up
    another remote:

        git remote add origin-push $(git config remote.origin.url)
        git fetch origin-push

    Now when the background process runs git fetch origin the references on origin-push won't be updated, and thus commands like:

        git push --force-with-lease origin-push

    Will fail unless you manually run git fetch origin-push. This method is of course entirely defeated by something that runs git
    fetch --all, in that case you'd need to either disable it or do something more tedious like:

        git fetch              # update 'master' from remote
        git tag base master    # mark our base point
        git rebase -i master   # rewrite some commits
        git push --force-with-lease=master:base master:master

    I.e. create a base tag for versions of the upstream code that you've seen and are willing to overwrite, then rewrite history, and
    finally force push changes to master if the remote version is still at base, regardless of what your local remotes/origin/master
    has been updated to in the background.

-f, --force
    Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it. Also, when
    --force-with-lease option is used, the command refuses to update a remote ref whose current value does not match what is expected.

    This flag disables these checks, and can cause the remote repository to lose commits; use it with care.

    Note that --force applies to all the refs that are pushed, hence using it with push.default set to matching or with multiple push
    destinations configured with remote.*.push may overwrite refs other than the current branch (including local refs that are strictly
    behind their remote counterpart). To force a push to only one branch, use a + in front of the refspec to push (e.g git push origin
    +master to force a push to the master branch). See the <refspec>...  section above for details.

--repo=<repository>
    This option is equivalent to the <repository> argument. If both are specified, the command-line argument takes precedence.

-u, --set-upstream
    For every branch that is up to date or successfully pushed, add upstream (tracking) reference, used by argument-less git-pull(1)
    and other commands. For more information, see branch.<name>.merge in git-config(1).

--[no-]thin
    These options are passed to git-send-pack(1). A thin transfer significantly reduces the amount of sent data when the sender and
    receiver share many of the same objects in common. The default is --thin.

-q, --quiet
    Suppress all output, including the listing of updated refs, unless an error occurs. Progress is not reported to the standard error
    stream.

-v, --verbose
    Run verbosely.

--progress
    Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified. This
    flag forces progress status even if the standard error stream is not directed to a terminal.

--no-recurse-submodules, --recurse-submodules=check|on-demand|only|no
    May be used to make sure all submodule commits used by the revisions to be pushed are available on a remote-tracking branch. If
    check is used Git will verify that all submodule commits that changed in the revisions to be pushed are available on at least one
    remote of the submodule. If any commits are missing the push will be aborted and exit with non-zero status. If on-demand is used
    all submodules that changed in the revisions to be pushed will be pushed. If on-demand was not able to push all necessary revisions
    it will also be aborted and exit with non-zero status. If only is used all submodules will be recursively pushed while the
    superproject is left unpushed. A value of no or using --no-recurse-submodules can be used to override the push.recurseSubmodules
    configuration variable when no submodule recursion is required.

--[no-]verify
    Toggle the pre-push hook (see githooks(5)). The default is --verify, giving the hook a chance to prevent the push. With
    --no-verify, the hook is bypassed completely.

-4, --ipv4
    Use IPv4 addresses only, ignoring IPv6 addresses.

-6, --ipv6
    Use IPv6 addresses only, ignoring IPv4 addresses.

使用示例

# 上传本地指定分支到远程仓库
$ git push [remote] [branch]

# 强行推送当前分支到远程仓库,即使有冲突
$ git push [remote] --force

# 推送所有分支到远程仓库
$ git push [remote] --all

查看更多 git push 命令的使用方法,可以使用命令:

git help push
网站项目管理

网站项目管理

[美] 阿什利·弗里德莱因 / 李保庆、杨磊、王增东 / 电子工业出版社 / 2002-11 / 32.00元

这本书全方位地介绍了如何建立和最终交付一个具有很高商业价值的成功网站,讲解从项目管理的角度入手,撇开烦琐的技术细节,更加关注Web项目实施中诸如成本、进度、工作范围等问题,涉及了一个商业网站在实施过程中可能遇到的所有管理细节。书内附国际一流网站开发专家的深邃见解;涵盖了网络项目管理的关键原则及案例研究;通过友情链接,还为读者提供了模板、论坛、术语表、相关链接以及有关因特网知识的测验题。一起来看看 《网站项目管理》 这本书的介绍吧!

图片转BASE64编码

图片转BASE64编码

在线图片转Base64编码工具

随机密码生成器

随机密码生成器

多种字符组合密码

XML 在线格式化

XML 在线格式化

在线 XML 格式化压缩工具