This helps to make sure that you are at least not overwriting work from others: it will present an error message and refuse to push if the remote was modified since you last fetched.You know testing your code is important-but how effective are your tests? How many lines of code does it address, and does it touch enough of the subroutines? Code coverage is the measurement of how much of your source code a test covers, and understanding it can go a long way toward being confident in your test results. The push command has another option called -force-with-lease. Use -force-with-lease instead of -force.This provides a much less obtrusive way to undo a mistake. However, consider using a tool that does NOT rewrite commit history, like git revert for example.
The basic need for a tool to correct a mistake that you've already pushed, of course, remains. If, on the other hand, you were working on a feature branch that only you yourself are using, then of course feel free to step on the gas and use the -force option. Whenever you have pushed commits to a remote branch that is shared with your team, you should try NOT to use force push. Since it is so easy to destroy or at least impede your colleagues' work, here are a few "safety rules" around git push -force: Your "force push" changes this history and means theirs is not in line with the new one anymore. Also, even if no one else has pushed anything to the remote repository in the meantime, your colleagues might still have based their new work on the old commit history. This is a rather dangerous process, because it's very easy to overwrite (and thereby lose) commits from your colleagues. The -force option for git push allows you to override this rule: the commit history on the remote will be forcefully overwritten with your own local history. Only when you are up-to-date will you be able to push your own new commits to the remote. As described above, Git will normally only allow you to push your changes if you have previously updated your local branch with the latest commits from its remote counterpart.
0 kommentar(er)
