bcooksley added a comment.
Anyone who has already pulled in the latest changes will need to forcibly reset their local working tree after the force push is completed. Should they have staged work, this would need to be rebased, which can be a non-trivial process and one many developers will not be familiar with. For those inexperienced with Git, forcibly resetting their local working copy is often not possible and the only way for them to get back to a usable state is for them to completely erase and re-clone the repository. In addition, should they have staged changes, the history of those changes could be lost (unless extreme care were taken) and in some cases people have accidentally erased work they've already completed. For these reasons Force Pushes are generally reserved for situations where no other option is available to correct the issue. REPOSITORY R8 Calligra REVISION DETAIL https://phabricator.kde.org/D16721 To: ognarb, #calligra:_3.0, anthonyfieroni Cc: bcooksley, anthonyfieroni, Calligra-Devel-list, dcaliste, cochise, vandenoever
