id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 20953,git push -f in docs needs a stern warning,Daniele Procida,nobody,"https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/#rebasing-branches: {{{ git push -f origin ticket_xxxxx }}} This should be accompanied by a note saying something like: '''Never''' use `push -f` without specifying a remote, otherwise you may be force-pushing changes to one or more unexpected remotes without even realising it. If you force-push to the wrong remote, you ''will'' be sorry. Ways of avoiding accidents with `push -f` include: * thinking twice and three times before using `push -f` * never using `push -f`, and instead: * deleting the branch on GitHub and pushing again, or: * creating a new local branch with `git checkout -b and pushing that * using a password (Git with HTTPS) rather than your key (Git with SSH) for your remotes' URLs (perhaps there are some more elegant solutions).",Cleanup/optimization,closed,Documentation,dev,Normal,wontfix,,,Accepted,0,0,0,0,0,0