hg push [-f] [-r REV]... [-e CMD] [--remotecmd CMD] [DEST]

push changes to the specified destination

    Push changesets from the local repository to the specified destination.

    This operation is symmetrical to pull: it is identical to a pull in the
    destination repository from the current one.

    By default, push will not allow creation of new heads at the destination,
    since multiple heads would make it unclear which head to use. In this
    situation, it is recommended to pull and merge before pushing.

    Use --new-branch if you want to allow push to create a new named branch
    that is not present at the destination. This allows you to only create a
    new branch without forcing other changes.

    Use -f/--force to override the default behavior and push all changesets on
    all branches.

    If -r/--rev is used, the specified revision and all its ancestors will be
    pushed to the remote repository.

    Please see "hg help urls" for important details about "ssh://" URLs. If
    DESTINATION is omitted, a default path will be used.

    Returns 0 if push was successful, 1 if nothing to push.


 -f --force                 force push
 -r --rev REV [+]           a changeset intended to be included in the
 -B --bookmark BOOKMARK [+] bookmark to push
 -b --branch BRANCH [+]     a specific branch you would like to push
    --new-branch            allow pushing a new branch
 -e --ssh CMD               specify ssh command to use
    --remotecmd CMD         specify hg command to run on the remote side
    --insecure              do not verify server certificate (ignoring
                            web.cacerts config)

[+] marked option can be specified multiple times

use "hg -v help push" to show more info