#4724: Force pushing master should not be allowed
-------------------------------------+-------------------------
Reporter: Janson | Owner:
Type: bug | Status: new
Priority: normal | Milestone: unspecified
Component: other | Version: git/master
Operating System: All/Non-Specific |
-------------------------------------+-------------------------
Forgon2100 force-pushed master from cef6b6a to e2a4e25
You guys should NEVER allow this! Fix your settings on github!
'''It's well known that git's push --force is strongly discouraged as it
can destroy other commits already pushed to a shared repository. This
isn't always completely fatal (if the changes are in someone's working
tree then they can be merged), but at the very least it's inconsiderate,
at worst disastrous. This is because the --force option makes the head of
the branch point at your personal history, ignoring any changes that may
have occurred in parallel with yours.'''
If you guys have a seriously crazy reason to force push then use git push
--force-with-lease
Now the repository is missing commits that once was there!
--
Ticket URL: <http://developer.wz2100.net/ticket/4724>
Warzone 2100 Trac <http://developer.wz2100.net/>
The Warzone 2100 Project
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Warzone2100-project mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/warzone2100-project
