This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
Force pushing master should not be allowed #4724
Labels
Milestone
Comments
|
Per changed blocking which not transferred by tractive |
|
Per changed blockedby which not transferred by tractive |
|
Forgon changed status from |
|
Forgon changed resolution from `` to |
|
Forgon commented In response to my blunder, Per has permanently disabled force-pushing to our main repository (read this forum thread). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
resolution_fixedtype_bug| by JansonForgon2100 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!
Issue migrated from trac:4724 at 2022-04-16 13:01:34 -0700
The text was updated successfully, but these errors were encountered: