Unable to force a push: missing force-push permission

Problem Solution

Problem	Solution
Some organizations allow one or more special users or administrators to overwrite other people’s work by granting this user the `force-push` permission. The `force-push` permission implies the powers associated with the following permissions: `read`, `write-ref`, `write-all`, `create-ref` and `delete-ref`. If the user does not have the `force-push` permission, git push --force origin master results in remote: ! [remote rejected] d59...2bf - master (User bruno does not have force-push privilege for reference refs/heads/master.)	Grant the `force-push` permission to the special user. p4 grant-permission -u bruno -p force-push -d gD1 See p4 grant-permission in Helix Core Command-Line (P4) Reference.

Some organizations allow one or more special users or administrators to overwrite other people’s work by granting this user the force-push permission. The force-push permission implies the powers associated with the following permissions: read, write-ref, write-all, create-ref and delete-ref.

If the user does not have the force-push permission,

git push --force origin master

results in

remote:  ! [remote rejected]
d59...2bf - master
(User bruno does not
have force-push privilege for
reference refs/heads/master.)

Grant the force-push permission to the special user.

p4 grant-permission -u bruno -p force-push -d gD1

See p4 grant-permission in Helix Core Command-Line (P4) Reference.